Darren Shaw created SOLR-18245:
----------------------------------
Summary: Add reRerankCutoff Output For LTR Based Sorts
Key: SOLR-18245
URL: https://issues.apache.org/jira/browse/SOLR-18245
Project: Solr
Issue Type: Improvement
Components: ltr
Reporter: Darren Shaw
h1. Context
When using LTR, a client may need to know the sort score that a document would
have required to have been eligible for rerank by LTR.
This is best illustrated by the following real-world example.
h2. Example Use Case
Solr is used in a retail environment where documents represent products. One
element that contributes to the sort score and therefore the document ordering
is a field called {{{}commercialUplift{}}}. This allows the retailer to
increase the score of a document due to commercial factors that are not
directly tied to the relevance of the document.
This {{commercialUplift}} is just one element used in the sort scoring function.
Given a page of results the retailer needs to to know the sort score another
document would require to have been included in that page and therefore the
{{commercialUplift}} value that would have been needed to increase a document's
score enough to get in to that page.
With a non-LTR search it is possible to do this by retrieving the sort score of
the lowest ranked document in a page of results.
But with LTR and its two stage ranking, in cases where the {{reRankDocs}} size
is greater than the page size ({{{}rows{}}}) and all documents are not
re-ranked, this is not possible. As well as the rerank scores output in the
final page of results, the retailer would need to know the original sort score
required for a document to have been included in the rerank stage (the score of
the lowest ranked document in the main sort scoring, before re-ranking).
h1. Requirement
Add a parameter to LTR queries to output a rerank cutoff value in the response
header. This value would be the original sort value(s) of the lowest ranked
document that was eligible for reranking.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
