[
https://issues.apache.org/jira/browse/SOLR-17732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942282#comment-17942282
]
ASF subversion and git services commented on SOLR-17732:
--------------------------------------------------------
Commit fcf0caca7fac47d1bb5e0e558ed6e201fa2ee703 in solr's branch
refs/heads/branch_9x from Siju Varghese
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=fcf0caca7fa ]
SOLR-17678, SOLR-17732: Add matchScore support for ReRank queries (#3222)
* Add support to return match score ( the query score ) in case of rerank query.
* Update Transformer code to be easier to extend
* Compute distributed score fields in first pass, then pass to return fields
Co-authored-by: Houston Putman <hous...@apache.org>
(cherry picked from commit b226f4726f22b699332f617f1393b5d1ccb45d74)
> Improve score returning logic for distributed requests
> ------------------------------------------------------
>
> Key: SOLR-17732
> URL: https://issues.apache.org/jira/browse/SOLR-17732
> Project: Solr
> Issue Type: Bug
> Reporter: Houston Putman
> Priority: Major
>
> Currently, returning the "score" field in a distributed request works well.
> However, any other type of "score" field, such as an alias
> (\{{score_alias:score}}), will omit the field in the response. This is
> because "score" is hardcoded in the QueryComponent.
> Instead, SolrReturnFields should have a concept of "score-dependent-fields",
> that get fetched during the GET_TOP_IDS step, and merged in to the final
> document during "returnFields()", just like "score" is currently.
> We can also improve the logic to determine if we should do a distributed
> single pass if only score-dependent-fields and the primary key field are
> requested.
--
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
