Lucene - Core
  1. Lucene - Core
  2. LUCENE-820

SegmentReader.setNorm can fail to remove separate norms file, on Windows

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.2
    • Component/s: core/index
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      While working through LUCENE-710 I hit this bug: on Windows
      only, when SegmentReader.setNorm is called, but separate norms
      (_X_N.sY) had already been previously saved, then, on closing the
      reader, we will write the next gen separate norm file correctly
      (_X_N+1.sY) but fail to delete the current one.

      It's quite minor because the next writer to touch the index will
      remove the stale file.

      This is because the Norm class still holds the IndexInput open when
      the reader commits.

      1. LUCENE-820.patch
        11 kB
        Michael McCandless

        Activity

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development