[ https://issues.apache.org/jira/browse/LUCENE-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615006#comment-13615006 ]
Eks Dev commented on LUCENE-4872: --------------------------------- the same pattern like Simon here, just having these terms wrapped in fuzzy/prefix query, often as dismax query. for example: BQ(boo* OR hoo* OR whatever) with e.g. minShouldMatch = 2 So the only diff to Simon's case is that single boolean clauses are often more complicated then simple TermQuery > 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: 5.0, 4.3 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org