[
https://issues.apache.org/jira/browse/LUCENE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241894#comment-16241894
]
Nathan Gass commented on LUCENE-8038:
-------------------------------------
{quote}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.
{quote}
Just for the record: As the calculated floats are not restricted anyway I don't
think optimizations like this are possible/impossible depending on that sort of
flexibility. You have/can add the exact same rules and constraints both ways.
> 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]
