[
https://issues.apache.org/jira/browse/LUCENE-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487188#comment-17487188
]
ASF subversion and git services commented on LUCENE-10407:
----------------------------------------------------------
Commit 8e5a88f2d5ec68b98ff8898b42686ad7fe5216d7 in lucene's branch
refs/heads/branch_9x from Alan Woodward
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=8e5a88f ]
LUCENE-10407: Set bpos flag to true when containing filter is exhausted (#648)
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. This commit
fixes that omission.
> 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
> 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
