[
https://issues.apache.org/jira/browse/LUCENE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286757#comment-17286757
]
Michael Sokolov commented on LUCENE-9640:
-----------------------------------------
Top N would cover most of the use cases we've been discussing, yes, so maybe
Explain is a viable approach. I was worrying about performance, maybe too much.
We can try that and see.
> Add TrackingQuery to track matching documents
> ---------------------------------------------
>
> Key: LUCENE-9640
> URL: https://issues.apache.org/jira/browse/LUCENE-9640
> Project: Lucene - Core
> Issue Type: New Feature
> Components: core/search
> Reporter: Elbek Kamoliddinov
> Priority: Major
> Labels: query
>
> Some users benefit having {{TrackingQuery}} functionality. This query would
> wrap another query and should be able to provide the matched DocIds for the
> wrapped query after search is run. For example a user running a boolean
> query {{A or B}} could wrap query {{A}} into {{TrackingQuery}} and run the
> boolean query and check if documents that matched the boolean query matches
> the query {{A}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
