[
https://issues.apache.org/jira/browse/LUCENE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286725#comment-17286725
]
Robert Muir commented on LUCENE-9640:
-------------------------------------
MIke its still a bit confusing to me (sorry, that kind of day): Is it true you
don't need this really on every matching document (e.g. no need for relying on
full DAAT traversal / large bitsets / slowing down query execution / preventing
WAND)... you just care about the top-N?
How different is what you want than invoking explain() on some of the top-N to
try to record some details about how they were ranked?
> 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: [email protected]
For additional commands, e-mail: [email protected]
