#54 – Elasticsearch w/ Wayne Fuller

This week on the podcast we welcome back Wayne Fuller to talk about Elasticsearch. Wayne gives an excellent introduction into using Elasticsearch with PeopleSoft, some lesson’s learned from his testing, and highlights the benefits of switching to the new search tool.

One quick note – after recording, Wayne got clarification that you cannot cut over to Elasticsearch by index, only by user. We’ll talk with Wayne in an upcoming episode again about that change so everybody has accurate information. -dan

We want to make this podcast part of the community discussion on PeopleSoft administration. If you have comments, feedback, or topics you’d like us to talk about, we want to hear from you! You can email us at podcast@psadmin.io, tweet us at @psa_io, or use the Twitter hashtag #psadminpodcast.

You can listen to the podcast here on psadmin.io or subscribe with your favorite podcast player using the URL below, or subscribe in iTunes.

Podcast RSS Feed

Show Notes

  • Testing Elasticsearch @ 1:00
  • Elasticsearch and IB Changes @ 5:00
  • Shards and Replicas @ 8:00
  • Elasticsearch Infrastructure @ 13:00
  • Elasticsearch Speed @ 17:15
  • Search Framework Architecture Changes @ 18:00
  • Integration Broker Impacts @ 25:00
  • Attachment Processing @ 28:00
  • Planning an Elasticsearch Deployment @ 31:30
  • Improving the Search Framework @ 38:30
  • Elasticsearch REST Interface @ 42:45
  • Health Center and Elasticsearch @ 46:00
  • Delete Processing @ 50:00
  • Beta Testing Experience @ 55:30

3 thoughts on “#54 – Elasticsearch w/ Wayne Fuller

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax