lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Busch (JIRA)" <>
Subject [jira] Commented: (LUCENE-730) Restore top level disjunction performance
Date Sun, 27 May 2007 17:09:16 GMT


Michael Busch commented on LUCENE-730:

> A slight improvement for the javadocs of
> In the javadocs of the scorer() method it is indicated that a BooleanScorer2
> will always be used, so it is better to mention here that BooleanScorer2
> delegates to a 1.4 scorer in some cases:

Maybe we should just deprecate the useScorer14 methods and add new methods
allowDocsOutOfOrder. That should be easier to understand for the users. 
And probably most users don't know (or don't care about) the differences
between BooleanScorer and BooleanScorer2 anyway.

> Restore top level disjunction performance
> -----------------------------------------
>                 Key: LUCENE-730
>                 URL:
>             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, 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:
For additional commands, e-mail:

View raw message