You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2018/07/23 13:18:00 UTC

[jira] [Created] (LUCENE-8423) The way IndexWriter carries over previous generations is fragile

Adrien Grand created LUCENE-8423:
------------------------------------

             Summary: 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


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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org