You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Adrien Grand <jp...@gmail.com> on 2017/12/06 13:25:10 UTC
Heads up: Lucene 8 to require positive scores
Hello,
I just merged a change to the Scorer contract: Scorer.score() must now
return a positive float, see
https://issues.apache.org/jira/browse/LUCENE-7996.
As a side effect, negative boosts are now disallowed.
Since FunctionScoreQuery and FunctionQuery can't ensure that the value
source only produces positive values, they return 0 when a negative value
is produced.
This might look like an annoying constraint, but this new requirement is
going to help build new features and optimizations, in particular
LUCENE-4100, which helps get great speedups for top-k queries sorted by
score.
Re: Heads up: Lucene 8 to require positive scores
Posted by Adrien Grand <jp...@gmail.com>.
Thanks for having a look Hoss, I added a new CHANGES entry under "Changes
in Runtime Behavior" (in addition to "API Changes") and added an upgrade
note in the solr changelog:
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f525ce8.
Le ven. 8 déc. 2017 à 23:29, Chris Hostetter <ho...@fucit.org> a
écrit :
>
> Adrien: shouldn't we have a note about this in the "Changes in Runtime
> Behavior" section of lucene/CHANGES.txt and the "Upgrade Notes" section of
> solr/CHANGES.txt for 8.0?
>
>
> : Date: Wed, 06 Dec 2017 13:25:10 +0000
> : From: Adrien Grand <jp...@gmail.com>
> : Reply-To: dev@lucene.apache.org
> : To: Lucene Dev <de...@lucene.apache.org>
> : Subject: Heads up: Lucene 8 to require positive scores
> :
> : Hello,
> :
> : I just merged a change to the Scorer contract: Scorer.score() must now
> : return a positive float, see
> : https://issues.apache.org/jira/browse/LUCENE-7996.
> :
> : As a side effect, negative boosts are now disallowed.
> :
> : Since FunctionScoreQuery and FunctionQuery can't ensure that the value
> : source only produces positive values, they return 0 when a negative value
> : is produced.
> :
> : This might look like an annoying constraint, but this new requirement is
> : going to help build new features and optimizations, in particular
> : LUCENE-4100, which helps get great speedups for top-k queries sorted by
> : score.
> :
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Heads up: Lucene 8 to require positive scores
Posted by Chris Hostetter <ho...@fucit.org>.
Adrien: shouldn't we have a note about this in the "Changes in Runtime
Behavior" section of lucene/CHANGES.txt and the "Upgrade Notes" section of
solr/CHANGES.txt for 8.0?
: Date: Wed, 06 Dec 2017 13:25:10 +0000
: From: Adrien Grand <jp...@gmail.com>
: Reply-To: dev@lucene.apache.org
: To: Lucene Dev <de...@lucene.apache.org>
: Subject: Heads up: Lucene 8 to require positive scores
:
: Hello,
:
: I just merged a change to the Scorer contract: Scorer.score() must now
: return a positive float, see
: https://issues.apache.org/jira/browse/LUCENE-7996.
:
: As a side effect, negative boosts are now disallowed.
:
: Since FunctionScoreQuery and FunctionQuery can't ensure that the value
: source only produces positive values, they return 0 when a negative value
: is produced.
:
: This might look like an annoying constraint, but this new requirement is
: going to help build new features and optimizations, in particular
: LUCENE-4100, which helps get great speedups for top-k queries sorted by
: score.
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org