[LUCENE-8145] UnifiedHighlighter should use single OffsetEnum rather than List<OffsetEnum>

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 7.3
• Component/s: modules/highlighter
• Lucene Fields: New
• Assignee: Alan Woodward
• Reporter: Alan Woodward
• Created: 31/Jan/18 15:52
• Updated: 28/Aug/22 15:24
• Resolved: 02/Feb/18 10:02

Description

The UnifiedHighlighter deals with several different aspects of highlighting: finding highlight offsets, breaking content up into snippets, and passage scoring.  It would be nice to split this up so that consumers can use them separately.

As a first step, I'd like to change the API of FieldOffsetStrategy to return a single unified OffsetsEnum, rather than a collection of them.  This will make it easier to expose the OffsetsEnum of a document directly from the highlighter, bypassing snippet extraction and scoring.

Issue Links

• relates to: LUCENE-8283 Improve FieldOffsetStrategy javadoc post-OffsetsEnum change
• links to: GitHub Pull Request #317