[
https://issues.apache.org/jira/browse/LUCENE-7517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595047#comment-15595047
]
Uwe Schindler commented on LUCENE-7517:
---------------------------------------
I agree here, especially with Robert's comment: We should store and return
scores as float to the user (a double makes no sense, because it leads to wrong
expectations for users - who always tend to misuse scores for stuff they are
not made for: they are just there to compare to search results and bring them
in right order; for that we should use the float, so minor calculation
differences don't matter). But when we actually calculate the score we should
use double precision for all calculation steps.
The good thing: at the end we round everything to a float, so some differences
by order of clauses would be removed during this round at end before it goes to
TopDocs.
> Explore making Scorer.score() return a double
> ---------------------------------------------
>
> Key: LUCENE-7517
> URL: https://issues.apache.org/jira/browse/LUCENE-7517
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Adrien Grand
> Priority: Minor
>
> Follow-up to
> http://search-lucene.com/m/l6pAi1BoyPJ1vr2382&subj=Re+JENKINS+EA+Lucene+Solr+master+Linux+64bit+jdk+9+ea+140+Build+18103+Unstable+.
> We could make Scorer.score() return a double in order to lose less accuracy
> when combining scores together, while still using floats on TopDocs and more
> generally all parts of the code that need to store scores.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
