You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by "Tim Kellogg (JIRA)" <ji...@apache.org> on 2013/04/25 18:58:15 UTC
[jira] [Created] (LUCENENET-520) IndexOutOfRangeException in
FieldInfos
Tim Kellogg created LUCENENET-520:
-------------------------------------
Summary: IndexOutOfRangeException in FieldInfos
Key: LUCENENET-520
URL: https://issues.apache.org/jira/browse/LUCENENET-520
Project: Lucene.Net
Issue Type: Bug
Components: Lucene.Net Core
Affects Versions: Lucene.Net 3.0.3, Lucene.Net 2.9.4g
Reporter: Tim Kellogg
Priority: Critical
Code Attached: Pull request is available at https://github.com/tkellogg/lucene.net/tree/FieldInfo-IndexOutOfRange
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira