Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <774730085.1131092240878.JavaMail.jira@ajax.apache.org>
Date: Fri, 4 Nov 2005 09:17:20 +0100 (CET)
From: "paul.elschot (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-395) CoordConstrainedBooleanQuery +
 QueryParser support
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/LUCENE-395?page=comments#action_12356754 ] 

paul.elschot commented on LUCENE-395:
-------------------------------------

>There are so many decision points in the creation of the scorers that I wrote a test to
> create random boolean queries to verify that things match the original. 

Thank you very much. I think there are not enough tests for boolean queries, so
such tests are very welcome.

> One thing I found is that when minNrShou ldMatch>0 with nested boolean queries, the
> scores may not match for those documents that match the same query with
> minNrShouldMatch=0. Is this expected? 

Yes, see also Hoss Mann's comment.
This can happen in the case that a nested query (eg. (E W Z) above) does
not match because of its minNrShould match,
while the full query still matches because it has enough
matching subqueries left.
In that case the full query has a smaller score because fewer of its subqueries match.

Btw. once this has settled I'd like to redo the splitting off the coordation part when
it is not needed, but that is only for performance.


> CoordConstrainedBooleanQuery + QueryParser support
> --------------------------------------------------
>
>          Key: LUCENE-395
>          URL: http://issues.apache.org/jira/browse/LUCENE-395
>      Project: Lucene - Java
>         Type: Improvement
>   Components: Search
>     Versions: unspecified
>  Environment: Operating System: other
> Platform: Other
>     Reporter: Mark Harwood
>     Assignee: Lucene Developers
>     Priority: Minor
>  Attachments: BooleanScorer2.java, CoordConstrainedBooleanQuery.java, CoordConstrainedBooleanQuery.java, CustomQueryParserExample.java, CustomQueryParserExample.java, LUCENE-395.patch, LUCENE-395.patch, LUCENE-395.patch, TestBooleanMinShouldMatch.java, TestBooleanMinShouldMatch.java, TestBooleanMinShouldMatch.java, TestBooleanMinShouldMatch.java, TestBooleanMinShouldMatch.java
>
> Attached 2 new classes:
> 1) CoordConstrainedBooleanQuery
> A boolean query that only matches if a specified number of the contained clauses
> match. An example use might be a query that returns a list of books where ANY 2
> people from a list of people were co-authors, eg:
> "Lucene In Action" would match ("Erik Hatcher" "Otis Gospodneti&#263;" "Mark Harwood"
> "Doug Cutting") with a minRequiredOverlap of 2 because Otis and Erik wrote that.
> The book "Java Development with Ant" would not match because only 1 element in
> the list (Erik) was selected.
> 2) CustomQueryParserExample
> A customised QueryParser that allows definition of
> CoordConstrainedBooleanQueries. The solution (mis)uses fieldnames to pass
> parameters to the custom query.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org