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

Binary field content lost during optimize

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.4, 2.9
    • 2.4.1, 2.9
    • core/index
    • None
    • Ubuntu 8.04, x86_64
      Java HotSpot(TM) 64-Bit Server VM (build 11.0-b15, mixed mode)

    • New

    Description

      Scenario:

      • create an index with arbitrary content, and close it
      • open IndexWriter again, and add a document with binary field (stored but not compressed)
      • close IndexWriter without optimizing, so that the new document is in a separate segment.
      • open IndexReader. You can read the last document and its binary field just fine.
      • open IndexWriter, optimize the index, close IndexWriter
      • open IndexReader. Now the field is still present (not null) and is marked as binary, but the data is not there - Field.getBinaryLength() returns 0.

      Attachments

        1. binaryField-junit.patch
          3 kB
          Andrzej Bialecki

        Activity

          People

            mikemccand Michael McCandless
            ab Andrzej Bialecki
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: