lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Woodward (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-8038) Decouple payload decoding from Similarity
Date Wed, 08 Nov 2017 09:14:00 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243566#comment-16243566
] 

Alan Woodward commented on LUCENE-8038:
---------------------------------------

PayloadScoreQuery just multiplies the score returned by the Similarity by a payload factor,
so it shouldn't interfere with any of the restrictions above.  For more flexibility, it might
be worth investigating a DoubleValuesSource that exposes payload factors that you could then
use in e.g. an Expression.  You'd then use the Expression as a sort field, which would bypass
LUCENE-4100 entirely.  That's for later though, I think the patch here is ready?

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message