[
https://issues.apache.org/jira/browse/LUCENE-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039743#comment-14039743
]
Michael McCandless commented on LUCENE-4396:
--------------------------------------------
bq. Solve the problem of score diff. between pure DAAT(ie. BS2, as BS2 does not
exist now, I think it may be better to call it pure DAAT) and BS completely.
That's great news! Looks like you separated required & optional
scores in the non-DAAT impls and then carefully cast to float at the
right times? Also, you can remove that TODO in ConjunctionScorer on
switching sum to double?
bq. Add a new Scorer named BooleanScorerInOrder which uses only bitset but not
linked list to collect docs.
So BooleanScorerIO is just like BooleanNovelScorer, except it uses a
bitset instead of linked list to track the set buckets? Between BNS
and BSIO which one is faster?
Why does BSIO/NS see massive gains on the tasks that have so many NOT
clauses? I think in trunk/4.x today, we are not scoring the NOT
clauses, right? While these gains are sizable, I think it's not a
common use case...
I think you've explored a number of options here and now we need to
see if we can make this committable, e.g. figure out how to have
BooleanQuery pick the right scorer for the situation? Somehow we need
logic that looks at how many / cost of the sub-clauses and picks the
right scorer?
> BooleanScorer should sometimes be used for MUST clauses
> -------------------------------------------------------
>
> Key: LUCENE-4396
> URL: https://issues.apache.org/jira/browse/LUCENE-4396
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Attachments: And.tasks, AndOr.tasks, AndOr.tasks, LUCENE-4396.patch,
> LUCENE-4396.patch, LUCENE-4396.patch, LUCENE-4396.patch, LUCENE-4396.patch,
> LUCENE-4396.patch, LUCENE-4396.patch, luceneutil-score-equal.patch,
> luceneutil-score-equal.patch
>
>
> Today we only use BooleanScorer if the query consists of SHOULD and MUST_NOT.
> If there is one or more MUST clauses we always use BooleanScorer2.
> But I suspect that unless the MUST clauses have very low hit count compared
> to the other clauses, that BooleanScorer would perform better than
> BooleanScorer2. BooleanScorer still has some vestiges from when it used to
> handle MUST so it shouldn't be hard to bring back this capability ... I think
> the challenging part might be the heuristics on when to use which (likely we
> would have to use firstDocID as proxy for total hit count).
> Likely we should also have BooleanScorer sometimes use .advance() on the subs
> in this case, eg if suddenly the MUST clause skips 1000000 docs then you want
> to .advance() all the SHOULD clauses.
> I won't have near term time to work on this so feel free to take it if you
> are inspired!
--
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
