[
https://issues.apache.org/jira/browse/LUCENE-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5615:
---------------------------------------
Attachment: LUCENE-5615.4x.patch
Patch for 4.x.
Good idea Rob: it'd be good to do some validation when we see a 3.x segment
that's being upgraded ... those files are clearly "oldish" and have more chance
of corruption.
I upgraded one assert in write3xInfo (verifying codec is correct) to a real
check. The only other thing I thought of is we could assert the files
referenced by the SI in fact exist (I haven't done that yet)? Anything else?
> 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
> Assignee: Michael McCandless
> Fix For: 4.8, 5.0
>
> Attachments: LUCENE-5615.4x.patch, 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]
