You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2015/03/31 10:51:53 UTC

[jira] [Created] (LUCENE-6382) Don't allow position = Integer.MAX_VALUE going forward

Michael McCandless created LUCENE-6382:
------------------------------------------

             Summary: Don't allow position = Integer.MAX_VALUE going forward
                 Key: LUCENE-6382
                 URL: https://issues.apache.org/jira/browse/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 position.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org