ceManager.doMaybeRefresh(ReferenceManager.java:154)
>> >at
>>
>>
>>org.apache.lucene.search.ReferenceManager.maybeRefreshBlocking(ReferenceManager.java:233)
>> >
>> >What am I doing wrong here?
>> >
>> >Thx,
>> >Vitaly
>> >
&
t; >> use IndexUpgrader, but this one would only merge if there are
> >segments
> >> created with an older Lucene version. You can change this by
> >overriding
> >> IndexUpgrader's merge policy to use all segments.
> >>
> >> You reminded me to op
; segments using a different codec configuration, not
>just
>> coming from an older Lucene version (which is possible to do).
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaph
remen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Vitaly Funstein [mailto:vfunst...@gmail.com]
> > Sent: Wednesday, May 15, 2013 11:36 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: Toggling compression
ler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Vitaly Funstein [mailto:vfunst...@gmail.com]
> Sent: Wednesday, May 15, 2013 11:36 PM
> To: java-user@lucene.apache.org
> Subject: Re: Toggling compression for
Thanks for the quick reply, this is certainly good news. So just to clarify
- doing a manual segment merge is optional when changing codecs, correct? I
mean, I can just restart my application with a new codec config and let the
regular, background merging task do the work of eventually converting a
Hi Vitaly,
what you call an "index" is just a collection (a CompositeReader) of atomic
readers. They can be mixed regarding compression, just like you could have a
MultiReader with different indexes using different codecs. Every atomic segment
of an index can only have one stored fields format.
