[jira] [Updated] (LUCENE-4872) BooleanWeight should decide how to execute minNrShouldMatch

["David Smiley (JIRA)" <ji...@apache.org>]

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

David Smiley updated LUCENE-4872:
---------------------------------

    Fix Version/s:     (was: 4.7)
                   4.8

> BooleanWeight should decide how to execute minNrShouldMatch
> -----------------------------------------------------------
>
>                 Key: LUCENE-4872
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4872
>             Project: Lucene - Core
>          Issue Type: Sub-task
>          Components: core/search
>            Reporter: Robert Muir
>             Fix For: 4.8
>
>         Attachments: crazyMinShouldMatch.tasks
>
>
> LUCENE-4571 adds a dedicated document-at-time scorer for minNrShouldMatch which can use advance() behind the scenes. 
> In cases where you have some really common terms and some rare ones this can be a huge performance improvement.
> On the other hand BooleanScorer might still be faster in some cases.
> We should think about what the logic should be here: one simple thing to do is to always use the new scorer when minShouldMatch is set: thats where i'm leaning. 
> But maybe we could have a smarter heuristic too, perhaps based on cost()



--
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