lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Created] (LUCENE-6382) Don't allow position = Integer.MAX_VALUE going forward
Date Tue, 31 Mar 2015 08:51:53 GMT
Michael McCandless created LUCENE-6382:

             Summary: Don't allow position = Integer.MAX_VALUE going forward
                 Key: LUCENE-6382
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Michael McCandless
            Assignee: Michael McCandless
             Fix For: Trunk, 5.2

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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message