lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <>
Subject [jira] [Closed] (LUCENENET-520) IndexOutOfRangeException in FieldInfos
Date Thu, 29 Jun 2017 11:18:00 GMT


Shad Storhaug closed LUCENENET-520.
    Resolution: Won't Fix

Lucene.Net 3.x is no longer being maintained, so I am closing as a won't fix.

I have also confirmed that the issue does not exist in Lucene.Net 4.8.0, since it is using
TryGetValue() of the dictionary to ensure if the key doesn't exist there is no exception.

> IndexOutOfRangeException in FieldInfos
> --------------------------------------
>                 Key: LUCENENET-520
>                 URL:
>             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,
pull request is located at
> 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 was sent by Atlassian JIRA

View raw message