[
https://issues.apache.org/jira/browse/LUCENE-6309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-6309:
--------------------------------
Attachment: LUCENE-6309.patch
Here is a patch. We already precompute coord(0..N, N), I just moved this to the
ctor and added checks.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
