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 oren.liat@gmail.com designates
 209.85.216.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=xWZmjELw29YomBg0IeMjDI9ZyaCoOpbdNPxp9YFqlOoQjL5posBkkNLBdoVvCvuKEB
         kQu212ZtUhZCaKc/rcsYor7uTId1hDpdTaWcVk2ERa6ou2//5bsuNnbMIPIsLgwWEk1z
         jKXFYf8rAeT42tBe0z+TYpIRvLt3MsHNgHQGY=
MIME-Version: 1.0
In-Reply-To: <004501cb5281$aacab020$00601060$@thetaphi.de>
References: <AANLkTi=3k_MW+EWN7OkN7W2o+2AhUUkMdBym+yAHBfq3@mail.gmail.com>
	<004501cb5281$aacab020$00601060$@thetaphi.de>
Date: Sun, 12 Sep 2010 23:29:17 +0300
Message-ID: <AANLkTikRh53pXh3rPV1M+u5fgC024QG9Xi_X_W+-F_39@mail.gmail.com>
Subject: Re: Unexpected Results - using should and must in boolean query
From: liat oren <oren.liat@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=00148502aee58401d5049015d5fa

--00148502aee58401d5049015d5fa
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Thanks for both of you for the answer.

I will try the solution of Uwe, it looks like your suggestion will solve my
problem.

Many thanks,
Liat


On 12 September 2010 16:51, Uwe Schindler <uwe@thetaphi.de> wrote:

> Hi,
>
> I always recommend my customers to not mix should and must in the same
> BooleanQuery if strict boolean matching is needed. It will match all docs,
> containing the MUST clause and "boost" all SHOULD terms.
>
> If you have some MUST terms, but you also want to have at least one of a
> list of other terms (like 5 SHOULD clauses), the trick is to separate both:
> Create a BooleanQuery with 2 MUST clauses, one is your required TermQuery
> and the second clause is itself a BooleanQuery with all the SHOULD clauses.
> This ensures that at least one of the SHOULD terms is needed together with
> the MUST term.
>
> Uwe
>
> -----
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: uwe@thetaphi.de
>
>
> > -----Original Message-----
> > From: liat oren [mailto:oren.liat@gmail.com]
> > Sent: Sunday, September 12, 2010 2:04 PM
> > To: java-user@lucene.apache.org
> > Subject: Unexpected Results - using should and must in boolean query
> >
> > Hi,
> >
> > I am running a query and get some unexpected results.
> >
> > When I run boolean query on a text field for the word X, using occur =
> SHOULD,
> > the results contain the word X.
> >
> > However, when I add another boolean query on another field (country) for
> the
> > word Y, using occur = MUST, in the results I get only documents in
> country
> Y,
> > but from some reason, not only that I get documents that don't contain
> the
> > word X, they get higher score than those contain the word X.
> >
> > If I change the occur of the word X in the query to MUST, it of course
> fixes it,
> > but I don't understand why the SHOULD "lost" its "power" when I added the
> > MUST on another field.
> >
> > Could something like this can happen?
> > How can it be solved?
> >
> > Many thanks,
> > Liat
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--00148502aee58401d5049015d5fa--