[
https://issues.apache.org/jira/browse/LUCENE-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894629#comment-15894629
]
Adrien Grand commented on LUCENE-7730:
--------------------------------------
I'm not sure we should do this, the fact that it is built into the similarity
allows to make trade-offs that are directly tight to the scoring formula. It's
true that we use the same encoding in our main similarities for convenience,
but I can imagine expert users would want to encode things in a special way
that reduces accuracy loss of the scoring formula?
> Better encode length normalization in similarities
> --------------------------------------------------
>
> Key: LUCENE-7730
> URL: https://issues.apache.org/jira/browse/LUCENE-7730
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
>
> Now that index-time boosts are gone (LUCENE-6819) and that indices record the
> version that was used to create them (for backward compatibility,
> LUCENE-7703), we can look into storing the length normalization factor more
> efficiently.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
