You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Andy Webb (Jira)" <ji...@apache.org> on 2023/02/02 13:30:00 UTC
[jira] [Updated] (SOLR-16643) Add multiplying boost option to ReRank query parser
[ https://issues.apache.org/jira/browse/SOLR-16643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Webb updated SOLR-16643:
-----------------------------
Description:
I noticed the ReRank query parser adds the score from the {{reRankQuery}} to the original score. This means that existing edismax {{boost}} functions can't easily be migrated to use reranking instead, and reranking functions have the same issue as is noted at https://solr.apache.org/guide/solr/latest/query-guide/dismax-query-parser.html#bq-bf-shortcomings.
In https://github.com/apache/solr/pull/1324 I've added a {{reRankOperator=multiply}} option to the ReRank parser which enables reranking functions to multiply the score instead.
Is this a good thing to do, or have I missed a reason why only additive boosts should be available?
was:
I noticed the ReRank query parser adds the score from the {{reRankQuery}} to the original score. This means that existing edismax {{boost}} functions can't easily be migrated to use reranking instead, and reranking functions have the same issue as is noted at https://solr.apache.org/guide/solr/latest/query-guide/dismax-query-parser.html#bq-bf-shortcomings.
In this PR (link coming shortly!) I've added a {{reRankOperator=multiply}} option to the ReRank parser which enables reranking functions to multiply the score instead.
Is this a good thing to do, or have I missed a reason why only additive boosts should be available?
> Add multiplying boost option to ReRank query parser
> ---------------------------------------------------
>
> Key: SOLR-16643
> URL: https://issues.apache.org/jira/browse/SOLR-16643
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Affects Versions: 9.1.1
> Reporter: Andy Webb
> Priority: Minor
>
> I noticed the ReRank query parser adds the score from the {{reRankQuery}} to the original score. This means that existing edismax {{boost}} functions can't easily be migrated to use reranking instead, and reranking functions have the same issue as is noted at https://solr.apache.org/guide/solr/latest/query-guide/dismax-query-parser.html#bq-bf-shortcomings.
> In https://github.com/apache/solr/pull/1324 I've added a {{reRankOperator=multiply}} option to the ReRank parser which enables reranking functions to multiply the score instead.
> Is this a good thing to do, or have I missed a reason why only additive boosts should be available?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org