jpountz commented on issue #13442:
URL: https://github.com/apache/lucene/issues/13442#issuecomment-2147633407
> A general framework on IndexSearcher sounds nice, but it's hard to
generalize with just this one use case?
Can it be something like IndexWriter's InfoStream, but for search? Or do we
need/want something more structured?
> Can we think of other queries/collectors that might also benefit from this?
Some examples that come to mind:
- Some users may want to know what fields are used for searching or
filtering in general, e.g. what percentage of queries are filtered by category?
by brand? by price?
- What clause(s) leads query evaluation.
- Number of hits that get evaluated vs. cost. (ie. how much is dynamic
pruning helping). Or maybe this one is too heavy and belongs to the query
profiler.
- What scorer is used, e.g. BS1 vs. BS2.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
