lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Khludnev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4236) clean up booleanquery conjunction optimizations a bit
Date Wed, 21 May 2014 18:57:45 GMT

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

Mikhail Khludnev commented on LUCENE-4236:
------------------------------------------

[~rcmuir] great job!

btw, i wonder if Solr is allowed to search with BooleanScorer (term-at-time)?

> 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, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message