lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Elschot (JIRA)" <>
Subject [jira] Commented: (LUCENE-1345) Allow Filter as clause to BooleanQuery
Date Sun, 11 Jan 2009 20:18:59 GMT


Paul Elschot commented on LUCENE-1345:

In case there is no score value for each matching document it is not possible to order the
results to be presented to a user. Because of that I don't want BooleanQuery to run correctly
without at least one normal query clause to provide a score to order the results. Putting
this in another way: TopDocs (and the meanwhile deprecated Hits) make no sense without at
least one normal query clause.

There are cases when all results are needed, and in that case for a Query one normally uses
to the HitCollector API. For Filters one could provide a MatchCollector API that collects
all hits providing only the document numbers, and no score (as in HitCollector). This was
part of the earlier versions of the patches at LUCENE-584 that introduced the new Filter API,
but it was dropped because it was new functionality that was not really needed at the time.
The same MatchCollector API can also be provided for Query searching. At that point, there
is no difference between Query and Filter.

> Allow Filter as clause to BooleanQuery
> --------------------------------------
>                 Key: LUCENE-1345
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Paul Elschot
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: booleansetperf.txt,, DisjunctionDISI.patch,
DisjunctionDISI.patch, LUCENE-1345-Filter+Query-merge.patch, LUCENE-1345.patch, LUCENE-1345.patch,,,

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