[
https://issues.apache.org/jira/browse/LUCENE-8043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16272238#comment-16272238
]
Simon Willnauer commented on LUCENE-8043:
-----------------------------------------
{quote}Turns out the test code that failed with a small amount of updates, even
after my attempted fix, was for 4.10.3 / 4.10.4
I forward-ported that code to master and things no longer fail... so I think
this patch is good for recent Lucene versions. Thanks!{quote}
[~yo...@apache.org] do you have a test case I can use to verify the patch going
forward? Can you share it? I will also try to turn your reproduction into a
testcase but maybe we should push the fix first to not be in the way of a
release, WDYT?
> Attempting to add documents past limit can corrupt index
> --------------------------------------------------------
>
> Key: LUCENE-8043
> URL: https://issues.apache.org/jira/browse/LUCENE-8043
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Affects Versions: 4.10, 7.0, master (8.0)
> Reporter: Yonik Seeley
> Assignee: Simon Willnauer
> Attachments: LUCENE-8043.patch
>
>
> The IndexWriter check for too many documents does not always work, resulting
> in going over the limit. Once this happens, Lucene refuses to open the index
> and throws a CorruptIndexException: Too many documents.
> This appears to affect all versions of Lucene/Solr (the check was first
> implemented in LUCENE-5843 in v4.9.1/4.10 and we've seen this manifest in
> 4.10)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
