[LUCENE-10140] Minimizing intervals can give inaccurate positions for duplicate terms

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 9.0
• Component/s: modules/queries
• Lucene Fields: New, Patch Available
• Assignee: Unassigned
• Reporter: Nikolay Khitrin
• Created: 30/Sep/21 14:38
• Updated: 28/Aug/22 16:27
• Resolved: 12/Oct/21 08:34

Description

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.

Issue Links

• links to: GitHub Pull Request #341
• links to: GitHub Pull Request #370