lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4872) BooleanWeight should decide how to execute minNrShouldMatch
Date Fri, 22 Mar 2013 14:15:15 GMT


Robert Muir commented on LUCENE-4872:

To really do this right I think we need a better tasks file for luceneutil probably too.
> BooleanWeight should decide how to execute minNrShouldMatch
> -----------------------------------------------------------
>                 Key: LUCENE-4872
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Sub-task
>          Components: core/search
>            Reporter: Robert Muir
>             Fix For: 5.0, 4.3
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message