[
https://issues.apache.org/jira/browse/LUCENE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240220#comment-16240220
]
Robert Muir commented on LUCENE-8038:
-------------------------------------
I want to urge caution about adding more flexibility. There is a huge benefit
in restricting what this can do: it can allow us to potentially implement stuff
like LUCENE-4100 and LUCENE-7993 for span queries.
But if we make them "ultra-flexible crap" with no rules or constraints then
these queries will just remain slow compared to e.g. phrase queries.
Can we just fix the API to be better on this issue without messing around with
any scoring of null or flexibility or anything else?
> Decouple payload decoding from Similarity
> -----------------------------------------
>
> Key: LUCENE-8038
> URL: https://issues.apache.org/jira/browse/LUCENE-8038
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Attachments: LUCENE-8038-master.patch, LUCENE-8038.patch
>
>
> PayloadScoreQuery is the only place that currently uses
> SimScorer.computePayloadFactor(), and as discussed on LUCENE-8014, this seems
> like the wrong place for it. We should instead add a PayloadDecoder
> abstraction that is passed to PayloadScoreQuery.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
