You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/13 13:26:41 UTC

[jira] [Commented] (LUCENE-7744) default value for scoring payloads

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

ASF GitHub Bot commented on LUCENE-7744:
----------------------------------------

GitHub user xabbu42 opened a pull request:

    https://github.com/apache/lucene-solr/pull/167

    LUCENE-7744

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/xabbu42/lucene-solr defaultpayload

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/lucene-solr/pull/167.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #167
    
----
commit fa0b3902b0cfe370bbbb259dca9b47723981bdb1
Author: Nathan Gass <ga...@search.ch>
Date:   2017-03-13T13:17:34Z

    let scorePayload provide a default for terms without payload

----


> default value for scoring payloads
> ----------------------------------
>
>                 Key: LUCENE-7744
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7744
>             Project: Lucene - Core
>          Issue Type: New Feature
>          Components: core/query/scoring
>            Reporter: Nathan Gass
>            Priority: Minor
>
> In lucene 5, PayloadTermQuery used a hardcoded default of 1.0 for terms without a payload. The replacing PayloadScoreQuery in lucene 6 just ignores those terms. This is unflexible and wrong for many use cases (for example using Payloads to deemphasize some terms, where terms without payload should result in maximum score instead of being ignored).
> In my pull request I defer the decision on what to do with missing payloads to the scorePayload method of the similarity, which has to check the given payload for null and handle that case. I believe this breaks backwards compatibility?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org