[
https://issues.apache.org/jira/browse/LUCENE-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286635#comment-17286635
]
Robert Muir commented on LUCENE-9640:
-------------------------------------
I really can't believe we'd take the hit to make something like Query mutable
for a corner-case, esp. when we don't even have a high-level use-case
described. this issue immediately jumped to implementation, reinventing filters
or highlighting or Scorer.getChildren for some unclear reason.
Don't mean it to come as an attack, but its similar to Scorer.getChildren
(which I equally hate): we need to take a step back and think about the
use-case and what other solutions might be appropriate. Maybe it should be a
highlighter functionality and not a Query, for example.
> 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
