[ 
https://issues.apache.org/jira/browse/LUCENE-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003860#comment-14003860
 ] 

ASF subversion and git services commented on LUCENE-4236:
---------------------------------------------------------

Commit 1596373 from [~rcmuir] in branch 'dev/branches/lucene4236'
[ https://svn.apache.org/r1596373 ]

LUCENE-4236: commit current state

> clean up booleanquery conjunction optimizations a bit
> -----------------------------------------------------
>
>                 Key: LUCENE-4236
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4236
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>             Fix For: 4.9, 5.0
>
>         Attachments: LUCENE-4236.patch, LUCENE-4236.patch, LUCENE-4236.patch, 
> LUCENE-4236.patch, LUCENE-4236.patch
>
>
> After LUCENE-3505, I want to do a slight cleanup:
> * compute the term conjunctions optimization in scorer(), so its applied even 
> if we have optional and prohibited clauses that dont exist in the segment 
> (e.g. return null)
> * use the term conjunctions optimization when optional.size() == 
> minShouldMatch, as that means they are all mandatory, too.
> * don't return booleanscorer1 when optional.size() == minShouldMatch, because 
> it means we have required clauses and in general BS2 should do a much better 
> job (e.g. use advance).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to