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

Hoss Man updated LUCENE-395:
----------------------------

    Attachment: LUCENE-395.patch
                TestBooleanMinShouldMatch.java

I don't really understand BooleanScorer2 very much, but i thought I understaood 
it enough to take a stab at the changes paul suggested to incorperate this type 
offunctionality into BooleanQuery using DisjunctionSumScorer.

Not suprisingly, some of the new tests I wrote for this functionality don't 
pass.  I can't figure out what the problem is.  perhaps It will come to me 
later, but in the mean time I wanted to post what I had in case the problem is 
something really silly and trivial that I'm overlooking.

> 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: CoordConstrainedBooleanQuery.java, 
> CoordConstrainedBooleanQuery.java, CustomQueryParserExample.java, 
> CustomQueryParserExample.java, LUCENE-395.patch, 
> 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ć" "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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to