[jira] [Created] (LUCENE-10140) Minimizing intervals can give inaccurate positions for duplicate terms

["Nikolay Khitrin (Jira)" <ji...@apache.org>]

Nikolay Khitrin created LUCENE-10140:
----------------------------------------

             Summary: Minimizing intervals can give inaccurate positions for duplicate terms
                 Key: LUCENE-10140
                 URL: https://issues.apache.org/jira/browse/LUCENE-10140
             Project: Lucene - Core
          Issue Type: Bug
          Components: modules/queries
            Reporter: Nikolay Khitrin


Minimizing intervals (maybe just ORDERED and AT_LEAST, but not sure) can move sub iterators to non-sub-match position *inside* match window, but CachingMatchesIterator logic relies on heuristic that any position inside matching interval is a sub-match.

For example: ORDERED("a", "b", "a") over "a b a" highlights (report sub-matches) only "a <b>b</b> <b>a</b>", and ORDERED("a", "b", "a", "b", "a")  highlights only "a b <b>a</b> <b>b</b> <b>a</b>".

Looks like there is no way to determine the right moment to cache from caching iterator perspective, so I propose to add an interface allowing minimizing IntervalIterators notify sub-sources positioned at sub-match positions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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