Chris M. Hostetter created SOLR-17299:
-----------------------------------------
Summary: Redesign debug component / reranking to support
multi-stage debugging
Key: SOLR-17299
URL: https://issues.apache.org/jira/browse/SOLR-17299
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Chris M. Hostetter
It is currently not possible to get accurate {{debug=results}} (aka: explain)
information when using the {{reRankScale}} option of query reanking in a
distributed cloud request w/o using {{distrib.singlePass=true}}
[This is because|https://issues.apache.org/jira/browse/SOLR-16931]...
bq. ...in order to do proper explain for minMaxScaling you need to know the min
and max score in the result set. This piece of state is maintained in the
ReRankScaler itself which is inside of the ReRankQuery. But for this
information to be populated the query must first be run. In distributed mode,
explain is called in the second pass when the ids query is run so the state
needed for the explain is not populated. ...
This ticket exists to track possible future work for improving the design of
either the debug component, or the reranker, so that the necessary information
can be communicated across multiple stages of a multi-stage distributed request
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
