You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2014/03/03 21:08:22 UTC
[jira] [Created] (LUCENE-5487) Can we separate "top scorer" from
"sub scorer"?
Michael McCandless created LUCENE-5487:
------------------------------------------
Summary: Can we separate "top scorer" from "sub scorer"?
Key: LUCENE-5487
URL: https://issues.apache.org/jira/browse/LUCENE-5487
Project: Lucene - Core
Issue Type: Improvement
Components: core/search
Reporter: Michael McCandless
Assignee: Michael McCandless
This is just an exploratory patch ... still many nocommits, but I
think it may be promising.
I find the two booleans we pass to Weight.scorer confusing, because
they really only apply to whoever will call score(Collector) (just
IndexSearcher and BooleanScorer).
The params are pointless for the vast majority of scorers, because
very, very few query scorers really need to change how top-scoring is
done, and those scorers can *only* score top-level (throw throw UOE
from nextDoc/advance). It seems like these two types of scorers
should be separately typed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org