[ https://issues.apache.org/jira/browse/LUCENE-7744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik Hatcher updated LUCENE-7744: --------------------------------- Fix Version/s: master (7.0) > 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 > Fix For: master (7.0) > > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org