[
https://issues.apache.org/jira/browse/LUCENE-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470627#comment-16470627
]
David Smiley commented on LUCENE-8306:
--------------------------------------
Aha; so this is the solution highlighters need. A good start. Do you think
the concrete class vs interface choice matters? If it's an interface then in
theory you could provide a view into the PostingsEnum's payload & other stuff
but the caller doesn't necessarily have to call it. This isn't a big deal
though. If you add getters instead of using public final fields, it'd be
easier to change later, and it's more standard style for a public API.
> Allow iteration over the term positions of a Match
> --------------------------------------------------
>
> Key: LUCENE-8306
> URL: https://issues.apache.org/jira/browse/LUCENE-8306
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Attachments: LUCENE-8306.patch
>
>
> For multi-term queries such as phrase queries, the matches API currently just
> returns information about the span of the whole match. It would be useful to
> also expose information about the matching terms within the phrase. The same
> would apply to Spans and Interval queries.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
