[
https://issues.apache.org/jira/browse/LUCENE-8014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220245#comment-16220245
]
Nathan Gass commented on LUCENE-8014:
-------------------------------------
As the computePayloadFactor change would break backwards compatibility anyway,
it may be appropriate to consider a solution for LUCENE-7744 at the same time.
In short, currently there is now way to influence how terms without payloads
get handled. So I would propose to make the change that computePayloadFactor
gets called for all terms (even without a payload) in the same release.
> Remove SimScorer.computeSlopFactor and SimScorer.computePayloadFactor
> ---------------------------------------------------------------------
>
> Key: LUCENE-8014
> URL: https://issues.apache.org/jira/browse/LUCENE-8014
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
>
> This supersedes LUCENE-8013.
> We should hardcode computeSlopFactor to 1/(N+1) in SloppyPhraseScorer and
> move computePayloadFactor to PayloadFunction so that all the payload scoring
> logic is in a single place.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
