[ 
https://issues.apache.org/jira/browse/LUCENE-8182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381350#comment-16381350
 ] 

Hoss Man commented on LUCENE-8182:
----------------------------------

FYI: [~jim.ferenczi] - it appears you commited this fix & CHANGES entry to 
branch_7x (6d712c5e4b2fc8f4ac6dfec2eac4a17386c978f0) but no CHANGES entry on 
master...

even if there is no fix needed on master, it's missing from the 7.3 section of 
CHANGES.txt on master, which is how i noticed it: it caused a conflict when 
added LUCENE-8188 to CHANGES and tried to back merge -- ideally even if no fix 
is needed on master, we should commit the CHANGES.txt entry there anyway.

> BoostingQuery applies the wrong boost to the query score
> --------------------------------------------------------
>
>                 Key: LUCENE-8182
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8182
>             Project: Lucene - Core
>          Issue Type: Bug
>    Affects Versions: 7.0, 7.1, 7.2
>            Reporter: Jim Ferenczi
>            Priority: Major
>             Fix For: 7.3
>
>         Attachments: LUCENE-8182.patch, LUCENE-8182.patch, LUCENE-8182.patch
>
>
> BoostingQuery applies the parent query boost instead of the boost set on the 
> query due to a name clash in the anonymous class created by the createWeight 
> method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to