lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Kellogg (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENENET-520) IndexOutOfRangeException in FieldInfos
Date Thu, 25 Apr 2013 17:00:18 GMT

     [ https://issues.apache.org/jira/browse/LUCENENET-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tim Kellogg updated LUCENENET-520:
----------------------------------

    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.

  was:
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.

    
> 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 2.9.4g, Lucene.Net 3.0.3
>            Reporter: Tim Kellogg
>            Priority: Critical
>              Labels: patch
>
> 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.

--
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

Mime
View raw message