[
https://issues.apache.org/jira/browse/LUCENE-8306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548981#comment-16548981
]
Alan Woodward commented on LUCENE-8306:
---------------------------------------
OK, how about this:
* getSubMatches() can be called at multiple levels, and returns null when
we're on a leaf
* label() returns something appropriate at each level: top-level queries at
the top level, matching Terms at the lowest level, and a Spans or
IntervalIterator object at intermediate levels
The other option for label() could be to go back to the idea of returning a
BytesRefIterator, so the top level would return all the currently matching
terms, and the leaf levels just a singleton iterator over the current term
> 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, LUCENE-8306.patch, 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
