[Building Sakai] Elastic Search (SRCH-111)

[Beth Kirschner]

I was wondering the same thing... I remember when discussing SOLR, the thought was that it would provide potential for new functionality (e.g. faceted search), but not address the scalability problems with search. The SRCH-111 JIRA states "The bulk of this work is simply a backend replacement that fixes most of the indexing/merging problems that have been experienced in large deployments...". This all sounds very promising. Has any of this been load tested? I'd like to put this on UM's load test calendar to compare results. I wonder if there's an opportunity to have configurable plugin options for a search back end?

- Beth

On Jan 24, 2013, at 8:39 AM, Adam Marshall wrote:

> Has this been discussed before? 
> 
> I mentioned to the list ages ago that we have reimplemented search using SOLR and nobody mentioned this elastic search work. We have been asked to contribute our SOLR work to 2.10 (by Chuck) - so I think we should have a discussion as to how our implementation and this Elastic search work should together.
> 
> adam
> 
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of Beth Kirschner
> Sent: 24 January 2013 13:36
> To: John Bush
> Cc: sakai-dev (sakai-dev at collab.sakaiproject.org)
> Subject: Re: [Building Sakai] Elastic Search (SRCH-111)
> 
> Thanks!
> 
> On Jan 23, 2013, at 8:12 PM, John Bush wrote:
> 
>> It's fixed, https://jira.sakaiproject.org/browse/SRCH-112, sorry about 
>> that did some refactoring for unit tests introduced that.
>> 
>> On Wed, Jan 23, 2013 at 5:58 PM, John Bush <john.bush at rsmart.com> wrote:
>>> hmm, that sounds like a bug, it should be 100% backwards compatible 
>>> with existing configuration.  Put a JIRA in and I'll address it.
>>> 
>>> On Wed, Jan 23, 2013 at 11:47 AM, Beth Kirschner <bkirschn at umich.edu> wrote:
>>>> Hi John,
>>>> 
>>>> The new elastic search (SRCH-111) does not seem to be backward compatible, as least for sakai.properties configuration. My sakai trunk build does not boot with "search.enable = true". I've attached the catalina.out file, but here's the first error:
>>>> 
>>>> 2013-01-23 10:41:35,127 ERROR Thread-3 
>>>> org.sakaiproject.search.elasticsearch.ElasticSearchIndexBuilder - 
>>>> Failed to load Stop words into Analyzer 
>>>> java.lang.NullPointerException
>>>> 
>>>> I'm not sure if this is intentional and the other specified sakai.properties (elasticsearch.http.*) need also need to be set or is this a bug? It will definitely break a lot of implementations as it stands. Perhaps I missed some email about this, but we should probably either update the JIRA to indicate properties changes will be _required_, or write this up as a new bug and make sure previous configurations will boot.
>>>> 
>>>> Thanks,
>>>> - Beth
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> John Bush
>>> 602-490-0470
>> 
>> 
>> 
>> --
>> John Bush
>> 602-490-0470
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"