[
https://issues.apache.org/jira/browse/LUCENE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973549#comment-13973549
]
Robert Muir commented on LUCENE-5615:
-------------------------------------
+1
Is there similar safety we can add to the scary 3.x upgraded si in 4.x? Just an
idea...
> validate per-segment delete counts on write
> -------------------------------------------
>
> Key: LUCENE-5615
> URL: https://issues.apache.org/jira/browse/LUCENE-5615
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Fix For: 4.8, 5.0
>
> Attachments: LUCENE-5615.patch
>
>
> When reading the segment infos, we already check if the delCount is out of
> bounds for a segment (< 0 or > docCount) and throw CorruptIndexException if
> so.
> I think we should catch this when writing as well, in case there are Lucene
> bugs that mess up the delete counts. We have just an assert today...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
