[
https://issues.apache.org/jira/browse/LUCENE-7996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16645147#comment-16645147
]
Yonik Seeley commented on LUCENE-7996:
--------------------------------------
bq. WAND and other optimizations were the reason why I opened this issue and
moved it forward
I understand why we wouldn't want to produce negative scores by default, as
that would complicate or prevent such optimizations by default.
What I don't understand is what we gain by prohibiting negative scores across
the board. We can only do these optimizations in certain cases anyway, so we
don't gain anything by prohibiting a function query (for example) from
producing negative values. This would seem to limit the use cases without any
corresponding gain in optimization opportunities.
> Should we require positive scores?
> ----------------------------------
>
> Key: LUCENE-7996
> URL: https://issues.apache.org/jira/browse/LUCENE-7996
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (8.0)
>
> Attachments: LUCENE-7996.patch, LUCENE-7996.patch, LUCENE-7996.patch
>
>
> Having worked on MAXSCORE recently, things would be simpler if we required
> that scores are positive. Practically, this would mean
> - forbidding/fixing similarities that may produce negative scores (we have
> some of them)
> - forbidding things like negative boosts
> So I'd be curious to have opinions whether this would be a sane requirement
> or whether we need to be able to cope with negative scores eg. because some
> similarities that we want to support produce negative scores by design.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
