lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <>
Subject Re: TieredMergePolicy and Doc ordering
Date Sat, 04 Jan 2014 10:23:31 GMT
Lucene's internal docIDs will change their order, but often this
doesn't matter and you won't see it.

E.g. if you search and you're sorting by your ID field then Lucene's
docID assignments has no effect.

It's only for tie-breaks where Lucene falls back to its docID to break the tie.

Mike McCandless

On Fri, Jan 3, 2014 at 5:16 AM, Ramprakash Ramamoorthy
<> wrote:
> Team,
> I'm using Lucene 4.4 and am indexing my documents using TieredMergePolicy.
> The documents I index have an incremental ID field. From the javadoc, I see
> that, tiered merge policy merges non adjacent segments.
> However, when I try to search through in my test environment, I get the
> search results in perfect order of incremental IDs. In case non adjacent
> segments are merged, then there should be a change in order of the IDs
> right? Or am I missing something?
> --
> With Thanks and Regards,
> Ramprakash Ramamoorthy,
> Chennai, India.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message