[
https://issues.apache.org/jira/browse/LUCENE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832931#action_12832931
]
Michael McCandless commented on LUCENE-1941:
--------------------------------------------
This is a real bug -- it happens because PayloadTermQuery (and
PayloadNearQuery) processPayload calls the payload scoring function, passing in
the old score and the new one.
The problem is the old score always defaults to 0.0. Ie it doesn't handle the
first payload properly -- first payload should set the value for min/max. So
you won't hit this if your min is < 0.
MaxPayloadFunction has the bug as well, but you won't hit it if your max is > 0.
> MinPayloadFunction returns 0 when only one payload is present
> -------------------------------------------------------------
>
> Key: LUCENE-1941
> URL: https://issues.apache.org/jira/browse/LUCENE-1941
> Project: Lucene - Java
> Issue Type: Bug
> Components: Query/Scoring
> Affects Versions: 2.9
> Reporter: Erik Hatcher
> Fix For: 3.0.1, 3.1
>
>
> In some experiments with payload scoring through PayloadTermQuery, I'm seeing
> 0 returned when using MinPayloadFunction. I believe there is a bug there.
> No time at the moment to flesh out a unit test, but wanted to report it for
> tracking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
