[
https://issues.apache.org/jira/browse/LUCENE-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward resolved LUCENE-10407.
------------------------------------
Fix Version/s: 9.1
Resolution: Fixed
> 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
> Priority: Major
> Fix For: 9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
