Improve Weight.scorer() API to enforce consistent topScorer/outOfOrder
parameters across segments
-------------------------------------------------------------------------------------------------
Key: LUCENE-3532
URL: https://issues.apache.org/jira/browse/LUCENE-3532
Project: Lucene - Java
Issue Type: Improvement
Components: core/search
Affects Versions: 4.0
Reporter: Uwe Schindler
Spinoff from LUCENE-1536: In the past, when filters were applied, all scorers
were forced to score in order. With random access DocIdSets, this is no longer
needed. Some Weights (BooleanWeight) unfortunately return different scorers for
in-order/out-of-order, leading to incompatible scores between segments.
For now we enforce in-order execution of scorers for FilteredQuery (as we do in
3.x), but once we fix BooleanWeight or have some other good way to produce
compatible scores, we can reenable random access. Maybe we should nuke
BooleanScorer2... - Robert and Mike have some ideas how to do that :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
