Re: TieredMergePolicy and Doc ordering

2014-01-05 Thread Ramprakash Ramamoorthy
Thank you Michael. On Sat, Jan 4, 2014 at 3:53 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > 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 ass

Re: TieredMergePolicy and Doc ordering

2014-01-04 Thread Michael McCandless
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 McCandl

TieredMergePolicy and Doc ordering

2014-01-03 Thread Ramprakash Ramamoorthy
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 resul