[
https://issues.apache.org/jira/browse/SOLR-3828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-3828.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0
Assignee: Hoss Man
Looking back at SOLR-2977 and r1222234 where these lines of code were added, i
think it was just a brain fart on grant's part -- he introduced a code branch
in a place where (previously) BooleanClauses were always added with MUST_NOT
and now that he didn't wnat to actaully exclude them, just mark them, he cloned
that code and had it use SHOULD instead.
but i agree, that doesn't make any sense -- the set of results using
markExclude=true should be the same as the set of results you get not using the
elevation component at all, and the scores of the excluded docs shouldn't
change.
Committed revision 1384567.
Committed revision 1384577. - 4x
Thanks for finding this and providing the test alexey!
> Query Elevation component boosts excluded results in markExcludes mode
> ----------------------------------------------------------------------
>
> Key: SOLR-3828
> URL: https://issues.apache.org/jira/browse/SOLR-3828
> Project: Solr
> Issue Type: Bug
> Components: SearchComponents - other
> Affects Versions: 4.0-BETA
> Reporter: Alexey Serba
> Assignee: Hoss Man
> Priority: Trivial
> Fix For: 4.0, 5.0
>
> Attachments: SOLR-3828.patch
>
>
> Query Elevation component boosts excluded results in markExcludes=true mode
> causing them to be higher on results than they should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
