Thank you, Trejkaz for your quick reply!
I definitelly updated my global constant
public static final Version VERSION = Version.LUCENE_30;
to
public static final Version VERSION = Version.LUCENE_36;
And performed total reindex as is recommended.
So the only option is to use old mergepolicy? Btw, I wonder is it
compatible with near realtime indexing?
On Wed, Apr 18, 2012 at 3:33 AM, Trejkaz <trej...@trypticon.org> wrote:
> On Wed, Apr 18, 2012 at 9:27 AM, Vladimir Gubarkov <xon...@gmail.com> wrote:
>> Hi, dear Lucene specialists,
>>
>> The only explanation I could think of is the new TieredMergePolicy
>> instead of old LogMergePolicy. Could it be that because of
>> TieredMergePolicy merges not adjacent segments - this results in not
>> preserving index order or this is total nonsense?
>
> TieredMergePolicy will definitely shuffle the order of docs in your
> index. But unless you provided a Version of Version.LUCENE_32 or later
> when constructing your IndexWriterConfig, it shouldn't be using that
> (and this won't happen automatically when you upgrade, unless you're
> doing something odd like using LUCENE_LATEST...)
>
> TX
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
