You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2018/07/23 13:24:00 UTC
[jira] [Commented] (LUCENE-8423) The way IndexWriter carries over
previous generations is fragile
[ https://issues.apache.org/jira/browse/LUCENE-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552853#comment-16552853 ]
Michael McCandless commented on LUCENE-8423:
--------------------------------------------
+1
> 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
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org