[
https://issues.apache.org/jira/browse/SOLR-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704729#comment-16704729
]
Adrien Grand commented on SOLR-13025:
-------------------------------------
Making the similarity depend on the compatibility version feels better for
backward compatibility at first, but it has downsides too. For instance if a
user was to search both 7.x and 8.x collections at once, then 7.x hits would
always get higher scores. It might be more user-friendly to just switch to
BM25Similarity and document the change in upgrade notes?
> Replace usage of LegacyBM25Similarity with BM25Similarity
> ---------------------------------------------------------
>
> Key: SOLR-13025
> URL: https://issues.apache.org/jira/browse/SOLR-13025
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Affects Versions: master (8.0)
> Reporter: Adrien Grand
> Assignee: Jan Høydahl
> Priority: Blocker
> Fix For: master (8.0)
>
>
> This is a follow-up of LUCENE-8563: Lucene changed its BM25Similarity
> implementation to no longer multiply all scores by (k1 + 1). Solr was left
> unchanged by replacing uses of BM25Similarity with LegacyBM25Similarity which
> returns the same scores as in 7.x. However it would be nice to switch back to
> BM25Similarity, either all the time with a note in the migration guide, or
> based on the luceneMatchVersion of the collection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
