[ https://issues.apache.org/jira/browse/LUCENE-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14494535#comment-14494535 ]
Michael McCandless commented on LUCENE-6382: -------------------------------------------- Good idea [~rcmuir] I'll move it there. > 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 > > Attachments: LUCENE-6382.patch, LUCENE-6382.patch, LUCENE-6382.patch > > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org