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

3.x -> 4.x .si upgrade should not be tricked by leftover upgrade marker file

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.10.5
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Today when you do the first IW.commit to a 3.x index from Lucene 4.x, we go
      through a per-segment upgrade process when writing the next segments_N
      file, writing .si files for each segment if we didn't already do so.

      However, this process can be fooled by a leftover _N_upgraded.si
      file, in case the app above Lucene wasn't careful and reused a
      directory that had leftover files... I think we can make this more
      robust.

        Attachments

        1. LUCENE-6279.patch
          3 kB
          Michael McCandless
        2. LUCENE-6279.patch
          2 kB
          Michael McCandless

          Activity

            People

            • Assignee:
              mikemccand Michael McCandless
              Reporter:
              mikemccand Michael McCandless
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: