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

Don't allow position = Integer.MAX_VALUE going forward

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2, 6.0
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      Spinoff from LUCENE-6308, where Integer.MAX_VALUE position is now used as a sentinel during position iteration to indicate that there are no more positions.

      Where IW now detects int overflow of position, it should now also detect == Integer.MAX_VALUE.

      And CI should note corruption if a segment's version is >= 5.2 and has Integer.MAX_VALUE position.

        Attachments

        1. LUCENE-6382.patch
          23 kB
          Michael McCandless
        2. LUCENE-6382.patch
          19 kB
          Michael McCandless
        3. LUCENE-6382.patch
          15 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: