[sakai-core-team] Issue with search in a cluster and old search components

Steve Swinsburg steve.swinsburg at gmail.com
Sun Aug 10 04:48:09 PDT 2014


+1 remove old search and just document it.


On Sat, Aug 9, 2014 at 9:48 AM, Earle Nietzel <enietzel at anisakai.com> wrote:

> +1 for removing old search unless there is someone who wants to maintain
> it.
>
>
>
>
> On Fri, Aug 8, 2014 at 6:57 PM, Matthew Jones <matthew at longsight.com>
> wrote:
>
>> Actually, thinking about this more and talking to a few people, I'm
>> leaning strongly on just removing all of the legacy search components and
>> writing up documentation for 10.1 if anyone really needs to continue using
>> them. I did that locally in about 15 minutes and it starts up okay. Going
>> to do some quick tests tonight but looks good so far. The only thing really
>> in search-impl left is the shims (which existed to plugin other search
>> components, mostly SOLR) and the content hosting digesters, which really
>> should be moved into content.
>>
>>
>> On Fri, Aug 8, 2014 at 6:23 PM, Matthew Jones <matthew at longsight.com>
>> wrote:
>>
>>> So by moving all of these components to shared to fix a problem with
>>> elastic search in a cluster in
>>> https://jira.sakaiproject.org/browse/SAK-27658 it broke the old search.
>>> This was because that used lucene 2.9, and elasticsearch used 4.5 (now 4.7
>>> but basically the same).
>>>
>>> In 10.0, elasticsearch was in it's own pack (elasticsearch-component)
>>> and it's had it's own version(s) of lucene so didn't conflict against the
>>> old search. Now that they're in shared, searck-pack has to use the shared
>>> version or it won't work.
>>>
>>> I worked on this for about half an hour and did the "easy upgrades"
>>> (imports/search replace) lowering the errors from about 200 to ~135. Now
>>> what's appear to be left are the medium and hard upgrades. Looking at the
>>> list, I'm betting it could take anywhere from a half day to a day to get
>>> these removed. The problem is there's not 100% guarantee it will work the
>>> same and the indexes will not work anyway (no support for 2.9 indexes)
>>>
>>> So the only option I can think of is to remove the old search files and
>>> beans completely from the search tool for 11 and 10.1. Nobody will want to
>>> run it if it's untested and doesn't work with their old data.
>>>
>>> If someone wants to run the old search, they would have to deploy 10.0
>>> search and help before these changes were made and remove lucene-* jars
>>> from shared.
>>>
>>> Any thoughts?
>>>
>>> https://jira.sakaiproject.org/browse/SAK-27788
>>>
>>
>>
>> _______________________________________________
>> sakai-core-team mailing list
>> sakai-core-team at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>>
>>
>
>
> --
> earle,
> asahi net int.
>
> _______________________________________________
> sakai-core-team mailing list
> sakai-core-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-core-team
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-core-team/attachments/20140810/4ad50c8d/attachment.html 


More information about the sakai-core-team mailing list