Hi Daniel,
2.3 should be no different from 2.2 in that docIDs only "shift" when
a merge of segments with deletions completes.
Could it be the ConcurrentMergeScheduler? Merges now run in the
background by default and commit whenever they complete. You can get
back to the previous (blocking) behavior by using
SerialMergeScheduler instead.
If it's not that ... can you provide more details about how your
applications is relying on docIDs?
Mike
Daniel Noll wrote:
Hi all.
We're using the document ID to associate extra information stored
outside
Lucene. Some of this information is being stored at load-time and
some
afterwards; later on it turns out the information stored at load-
time is
returning the wrong results when converting the database contents
back into a
BitSet for filtering.
Using version 2.2.x doesn't appear to cause the problem, so I have
been
wondering if something happened in 2.3.x to change the document
IDs. Having
already looked to try and determine this myself, it doesn't appear
to be
reordering them in DocumentsWriter, but perhaps there is some subtle
side-effect of the way segments are merged which has caused this?
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
