Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <1165670273.1128787429004.JavaMail.jira@ajax.apache.org>
Date: Sat, 8 Oct 2005 18:03:49 +0200 (CEST)
From: "paul.elschot (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Updated: (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=all ]

paul.elschot updated LUCENE-395:
--------------------------------

    Attachment: BooleanScorer2.java

This a continuation of the earlier patch.
The basic ideas are now built deep into the logic of determining the actual scorer to be used.
For this logic needed quite a few changes, simplifying in many places, but also
one more case (a conjunction scorer over (a) the required scorers and (b) a disjunction
scorer over optional scorers with a minimum number that should match).

This obsoletes another patch that splits off the coordination logic when it is not needed.
I'll note this there later.

Some tests for unchanged scoring behaviour are still needed, but those can
be added later, since this is probably going to work well.

Again, thanks for this idea and for the test cases.

Regards,
Paul Elschot


> 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
>
> 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