Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of gregdearing@gmail.com
 designates 74.125.82.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAASL1-9rkjMUYhK4M7o+v_XiAcMUK6ChtGO62Q-W-7RMvsp7uQ@mail.gmail.com>
References: 
 <CAJ8PQVxb2_z0zP2EY9=rkGHBo-uhTaPWBfjQgRddMH6CraMrkw@mail.gmail.com>
	<CAASL1-9rkjMUYhK4M7o+v_XiAcMUK6ChtGO62Q-W-7RMvsp7uQ@mail.gmail.com>
Date: Thu, 17 Apr 2014 11:22:33 -0400
Message-ID: 
 <CAASL1-_gtqgVxvgFfMkM=Tir0rUL+FbsaHL==RJyHVxSTZ=+zg@mail.gmail.com>
Subject: Re: BooleanScorer - Maximum Prohibited Scorers?
From: Gregory Dearing <gregdearing@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=f46d043c801e264b1904f73e9aa2

--f46d043c801e264b1904f73e9aa2
Content-Type: text/plain; charset=UTF-8

David,

I believe I misunderstood your question in my earlier response.

I think you can create a logical "MaximumNumberMustNotMatch" by nesting
Boolean Queries.

1.) Create a Boolean Query, using 'SHOULD' clauses and setting Minimum
Number Should Match.

2. ) Wrap the BooleanQuery with a 'MUST_NOT' BooleanClause.

3.) Add the negating BooleanClause to a second BooleanQuery.

-Greg


On Thu, Apr 17, 2014 at 10:40 AM, Gregory Dearing <gregdearing@gmail.com>wrote:

> David,
>
> Any document that matches a MUST_NOT clause will not match the
> BooleanQuery.  By definition.
>
> This means that "maximumNumberMustNotMatch" is effectively hardcoded to
> zero.
>
> -Greg
>
>
> On Wed, Apr 16, 2014 at 3:59 PM, David Stimpert <dave@genomoncology.com>wrote:
>
>> Hello,
>> I have found useful functionality in BooleanQuery which allows me to
>> specify a minimum number of matching optional terms
>> (i.e. setMinimumNumberShouldMatch).  I do not, however, see similar
>> functionality available for setting the maximum number of MUST_NOTs (i.e.
>> setMaximumNumberMustNotMatch).  I am starting to look into how I could
>> customize this functionality.  Does this seem feasible?  Do you foresee
>> any
>> major challenges?  Any advice?
>>
>
>

--f46d043c801e264b1904f73e9aa2--