lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: Solr Lucene Index Version
Date Wed, 07 Dec 2011 14:55:32 GMT
Jamie -

The details would of course be entirely dependent on what changed, but with Lucene trunk/4.0
there is the flexible indexing API with codecs.  I imagine with a compatibility codec layer
one could provide some insulation to changes.

You're at big scale, so the "just reindex everything" answer isn't really satisfactory I understand.
 But locking in to a version of Lucene may be a decent stop-gap solution, and if/when the
format changes you can upgrade one node at a time (the Solr request/response won't change!)
and reindex in a rolling manner probably.  Again, it's still risky as there may be changes
to the index format needed for enhancements to SolrCloud that you want so you'd be stuck at
a fixed place with SolrCloud until you could do some reindexing.


On Dec 7, 2011, at 08:50 , Jamie Johnson wrote:

> Erik,
> Do you have any details behind what would be required to write a tool
> to move from one index format to another?  Any examples/suggestions
> would be appreciated.
> On Tue, Dec 6, 2011 at 5:19 PM, Jamie Johnson <> wrote:
>> What about modifying something like to change the
>> lucene version that is used when creating the index?  (may not be the
>> right place, but is something like this possible?)
>> On Tue, Dec 6, 2011 at 5:13 PM, Erik Hatcher <> wrote:
>>> Right.  Not sure what to advise you.  We have worked on this problem with our
LucidWorks platform and have some tools available to do this sort of thing, I think, but it's
not generally something that you can do with Lucene going from a snapshot to a released version.
 Perhaps others with deeper insight will chime in.
>>>        Erik
>>> On Dec 6, 2011, at 16:54 , Jamie Johnson wrote:
>>>> Problem is that really doesn't help me.  We still have the same issue
>>>> that when the 4.0 becomes final there is no migration utility from
>>>> this pre 4.0 version to 4.0, right?
>>>> On Tue, Dec 6, 2011 at 4:36 PM, Erik Hatcher <>
>>>>> Oh geez... no... I didn't mean 3.x JARs... I meant the trunk/4.0 ones
that are there now.
>>>>>        Erik
>>>>> On Dec 6, 2011, at 16:22 , Jamie Johnson wrote:
>>>>>> So if I wanted to used lucene index 3.5 with SolrCloud I "should"
>>>>>> able to just move the 3.5 jars in and remove any of the snapshot
>>>>>> that are present when I build locally?
>>>>>> On Tue, Dec 6, 2011 at 4:06 PM, Erik Hatcher <>
>>>>>>> Jamie -
>>>>>>> I think the best thing that you could do here would be to lock
in a version of Lucene (all the Lucene libraries) that you use with SolrCloud.  Certainly
not out of the realm of possibilities of some upcoming SolrCloud capability that requires
some upgrading of Lucene though, but you may be set for a little while at least.
>>>>>>>        Erik
>>>>>>> On Dec 6, 2011, at 15:57 , Jamie Johnson wrote:
>>>>>>>> Thanks, but I don't believe that will do it.  From my understanding
>>>>>>>> that does not control the index version written, it's used
to control
>>>>>>>> the behavior of some analyzers (taken from some googling).
 I'd love
>>>>>>>> if someone told me otherwise though.
>>>>>>>> On Tue, Dec 6, 2011 at 3:48 PM, Alireza Salimi <>
>>>>>>>>> Hi, I'm not sure if it would help.
>>>>>>>>> in solrconfig.xml:
>>>>>>>>>  <!-- Controls what version of Lucene various components
of Solr
>>>>>>>>>       adhere to.  Generally, you want to use the latest
version to
>>>>>>>>>       get all bug fixes and improvements. It is highly
>>>>>>>>>       that you fully re-index after changing this setting
as it can
>>>>>>>>>       affect both how text is indexed and queried.
>>>>>>>>>    -->
>>>>>>>>>  <luceneMatchVersion>LUCENE_34</luceneMatchVersion>
>>>>>>>>> On Tue, Dec 6, 2011 at 3:14 PM, Jamie Johnson <>
>>>>>>>>>> Is there a way to specify the index version solr
uses?  We're
>>>>>>>>>> currently using SolrCloud but with the index format
changing I'd be
>>>>>>>>>> preferable to be able to specify a particular index
format to avoid
>>>>>>>>>> having to do a complete reindex.  Is this possible?
>>>>>>>>> --
>>>>>>>>> Alireza Salimi
>>>>>>>>> Java EE Developer

View raw message