Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-8423

The way IndexWriter carries over previous generations is fragile

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 7.5, 8.0
    • None
    • None
    • New

    Description

      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?

      Attachments

        1. LUCENE-8423.patch
          3 kB
          Adrien Grand

        Activity

          People

            Unassigned Unassigned
            jpountz Adrien Grand
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: