lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-5487) Can we separate "top scorer" from "sub scorer"?
Date Fri, 07 Mar 2014 21:04:43 GMT


Michael McCandless updated LUCENE-5487:

    Attachment: LUCENE-5487.patch

Applyable patch from the branch (generated by, I think it's ready.

> Can we separate "top scorer" from "sub scorer"?
> -----------------------------------------------
>                 Key: LUCENE-5487
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/search
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>         Attachments: LUCENE-5487.patch, LUCENE-5487.patch, LUCENE-5487.patch
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message