Interesting!
I would be inclined to allow this, and fix CheckIndex's paranoia. As
far as I can tell, Lucene itself does not mind if the position is -1
(at least PhraseQuery, SpanTermQuery happily find that Term at
position -1), although we do prevent setting positionIncrement to a
negat
Hi,
I'm using 2.3.0 Lucene build and have following merge parameters,
mergeFactor = 100
maxMergeDocs = 9
maxBufferedDocs = 1
maxRAMBufferSizeMB = 200
After running with this setting for a month without problem all the
sudden I'm getting following exception,
java.lang.IllegalArgumentE
