You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Robert Muir (Jira)" <ji...@apache.org> on 2021/03/05 00:07:00 UTC
[jira] [Commented] (LUCENE-9823) SynonymQuery rewrite can change
field boost calculation
[ https://issues.apache.org/jira/browse/LUCENE-9823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17295653#comment-17295653 ]
Robert Muir commented on LUCENE-9823:
-------------------------------------
+1
sounds like this rewrite is unsafe.
> SynonymQuery rewrite can change field boost calculation
> -------------------------------------------------------
>
> Key: LUCENE-9823
> URL: https://issues.apache.org/jira/browse/LUCENE-9823
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Julie Tibshirani
> Priority: Minor
>
> SynonymQuery accepts a boost per term, which acts as a multiplier on the term frequency in the document. When rewriting a SynonymQuery with a single term, we create a BoostQuery wrapping a TermQuery. This changes the meaning of the boost: it now multiplies the final TermQuery score instead of multiplying the term frequency before it's passed to the score calculation.
> This is a small point, but maybe it's worth avoiding rewriting a single-term SynonymQuery unless the boost is 1.0.
> The same consideration affects CombinedFieldQuery in sandbox.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org