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

Posted to issues@lucene.apache.org by "Alan Woodward (Jira)" <ji...@apache.org> on 2022/02/04 16:11:00 UTC

[jira] [Created] (LUCENE-10407) ContainingIntervalIterator can incorrectly report positions after exhaustion

Alan Woodward created LUCENE-10407:
--------------------------------------

             Summary: ContainingIntervalIterator can incorrectly report positions after exhaustion
                 Key: LUCENE-10407
                 URL: https://issues.apache.org/jira/browse/LUCENE-10407
             Project: Lucene - Core
          Issue Type: Bug
            Reporter: Alan Woodward
            Assignee: Alan Woodward


ContainedByIntervalIterator and OverlappingIntervalIterator set their 'is the filter interval exhausted' flag to `false` once it has returned NO_MORE_POSITIONS on a document, so that subsequent calls to `startPosition()` will also return NO_MORE_POSITIONS.  ContainingIntervalIterator omits to do this, and so it can incorrectly report matches, for example when used in a disjunction.

cc [~dweiss] 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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