[
https://issues.apache.org/jira/browse/LUCENE-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-8423.
----------------------------------
Resolution: Fixed
Fix Version/s: 7.5
master (8.0)
> The way IndexWriter carries over previous generations is fragile
> ----------------------------------------------------------------
>
> Key: LUCENE-8423
> URL: https://issues.apache.org/jira/browse/LUCENE-8423
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (8.0), 7.5
>
> Attachments: LUCENE-8423.patch
>
>
> IndexWriter won't carry over generation numbers if
> SegmentInfos#readLatestCommit fails with an IOException, even though the
> intention is to not carry over only if the index doesn't exist. I don't think
> it causes too many issues today since a number of IOExceptions like
> corruptions would be propagated by IndexFileDeleter later on, but we should
> still make it more robust?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
