[
https://issues.apache.org/jira/browse/LUCENE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499362
]
Doron Cohen commented on LUCENE-730:
------------------------------------
Two comments:
With this patch the class BooleanWeight is not
in (direct) use anymore - it is extended by
BooleanWeight2 and then only the latter is used,
and creates either Scorer2 or Scorer. We could
get rid of BolleanWeight2, and have a single
class BooleanWeight.
Javadocs for useScorer14 methods:
/**
* Indicates that 1.4 BooleanScorer should be used.
* Being static, This setting is system wide.
* Scoring in 1.4 mode may be faster.
* But note that unlike the default behavior, it does
* not guarantee that docs are collected in docid
* order. In other words, with this setting,
* [EMAIL PROTECTED] HitCollector#collect(int,float)} might be
* invoked first for docid N and only later for docid N-1.
*/
public static void setUseScorer14(boolean use14) {
/**
* Whether 1.4 BooleanScorer should be used.
* @see #setUseScorer14(boolean)
*/
public static boolean getUseScorer14() {
> Restore top level disjunction performance
> -----------------------------------------
>
> Key: LUCENE-730
> URL: https://issues.apache.org/jira/browse/LUCENE-730
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Paul Elschot
> Assigned To: Michael Busch
> Priority: Minor
> Fix For: 2.2
>
> Attachments: lucene-730.patch, TopLevelDisjunction20061127.patch
>
>
> This patch restores the performance of top level disjunctions.
> The introduction of BooleanScorer2 had impacted this as reported
> on java-user on 21 Nov 2006 by Stanislav Jordanov.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
