Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Won't Fix
-
Lucene.Net 2.9.4g, Lucene.Net 3.0.3
-
None
Description
Code Attached: Code is available at https://github.com/tkellogg/lucene.net/tree/FieldInfo-IndexOutOfRange, pull request is located at https://github.com/apache/lucene.net/pull/7
The `DIFFs FROM 2.9.4.txt` file indicates that the Java collections return
null when the index is out of bounds. I imagine that this bug was simply copied
from generally correct Java code and now is just simply not correct anymore.
Please stop me if this is actually an indication of a deeper problem, like
corruption of the index.
In the problem that I was observing, fieldNumber = 110 and byNumber.Count = 10,
Since the list index was 11x the size of the list, it feels like it indicates
data corruption in the index. I'm using MongoDB.Lucene's MongoFSDirectory, so
I'm concerned that could be at fault.