lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <>
Subject [jira] Commented: (LUCENE-1754) Get rid of NonMatchingScorer from BooleanScorer2
Date Mon, 27 Jul 2009 11:35:15 GMT


Shai Erera commented on LUCENE-1754:

bq. Is it really allowed to return null instead of an empty iterator?

Some iterators already return null as an iterator, perhaps unknowingly. QueryWrapperFilter
will do that if the Query produced a null Scorer, which is legal, or at least the de facto
impl of some Queries.

I think that the decisions on this issue were made because we observed that returning null
"already exists", and moving to not return null, or saying that null should not be returned,
may break back-compat (e.g. if someone relies on null to mean "there are no docs to match").

> Get rid of NonMatchingScorer from BooleanScorer2
> ------------------------------------------------
>                 Key: LUCENE-1754
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Shai Erera
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1754-2.patch, LUCENE-1754-2.patch, LUCENE-1754.patch, LUCENE-1754.patch,
LUCENE-1754.patch, LUCENE-1754.patch
> Over in LUCENE-1614 Mike has made a comment about removing NonMatchinScorer from BS2,
and return null in BooleanWeight.scorer(). I've checked and this can be easily done, so I'm
going to post a patch shortly. For reference:
> I've marked the issue as 2.9 just because it's small, and kind of related to all the
search enhancements done for 2.9.

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