[jira] [Resolved] (LUCENE-6309) disable coord when scores are not needed, or the scoring fn does not use it

["Robert Muir (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir resolved LUCENE-6309.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 5.1
                   Trunk

> disable coord when scores are not needed, or the scoring fn does not use it
> ---------------------------------------------------------------------------
>
>                 Key: LUCENE-6309
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6309
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Robert Muir
>             Fix For: Trunk, 5.1
>
>         Attachments: LUCENE-6309.patch
>
>
> In BooleanWeight when disableCoord is set, things are nicer. coord makes things complex (e.g. sometimes requires some crazy scorers in BooleanTopLevelScorers) and can block optimizations.
> We should also implicitly disableCoord when scores are not needed, or when the Similarity does not use coord().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org