You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2014/09/24 02:28:34 UTC

[jira] [Resolved] (LUCENE-5975) Lucene can't read 3.0-3.3 deleted documents

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

Robert Muir resolved LUCENE-5975.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 4.10.1

> Lucene can't read 3.0-3.3 deleted documents
> -------------------------------------------
>
>                 Key: LUCENE-5975
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5975
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Priority: Blocker
>             Fix For: 4.10.1
>
>         Attachments: LUCENE-5975.patch, LUCENE-5975.patch
>
>
> BitVector before Lucene 3.4 had many bugs, particulary that it wrote extra bogus trailing crap at the end.
> But since Lucene 4.8, we check that we read all the bytes... this check can fail for 3.0-3.3 indexes due to the previous bugs in those indexes, instead users will get exception on open like this: CorruptIndexException(did not read all bytes from file: read 5000 vs 5001....



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org