[
https://issues.apache.org/jira/browse/LUCENE-7730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894073#comment-15894073
]
Alan Woodward commented on LUCENE-7730:
---------------------------------------
Should we try and separate norms encoding from the different Similarity
implementations? It seems a bit odd to me that you have to set a Similarity on
IndexWriterConfig, but then you can use a completely different Sim at search
time and it will all still work, providing that it encodes norms in the same
way. Perhaps instead we should abstract out a NormsEncoding interface, which
gets passed both to IWC and to Similarity?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
