[LUCENE-10407] ContainingIntervalIterator can incorrectly report positions after exhaustion

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.1
• Lucene Fields: New
• Assignee: Alan Woodward
• Reporter: Alan Woodward
• Created: 04/Feb/22 16:10
• Updated: 28/Aug/22 16:35
• Resolved: 04/Feb/22 17:21

Description

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 

Issue Links

• links to: GitHub Pull Request #648