Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
MIME-Version: 1.0
Sender: ppp.pawelrog@gmail.com
In-Reply-To: <CAM21Rt92iWihuP-9oiAVC-jEJ7KBdqj63SvOBvzLvENX73gWXw@mail.gmail.com>
References: <CAF9ZkbNy9wVDsRViqfqqaQFPCXCydRV9AkmzFxesOT4X-ysWdg@mail.gmail.com>
 <CAN4YXvfeCTPv0KPZKeD4v3me=sp+4RdQQ45Buiv+ap66GogLiw@mail.gmail.com>
 <CAF9ZkbOMMgHk5=yV6aoX-Ps2bgV96W=cca+XYJ5=Bw8Q3Gz+xA@mail.gmail.com> <CAM21Rt92iWihuP-9oiAVC-jEJ7KBdqj63SvOBvzLvENX73gWXw@mail.gmail.com>
From: Pawel Rog <pawelrog88@gmail.com>
Date: Wed, 9 Nov 2016 23:26:28 +0100
Message-ID: <CAF9ZkbPn8u_+Y+YohPK25YC-8SeHzejJgz-0QU=CP7oNuaRBZA@mail.gmail.com>
Subject: Re: Query parser and default operator
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=001a11401dc6902c4a0540e5bf55
archived-at: Wed, 09 Nov 2016 22:26:41 -0000

--001a11401dc6902c4a0540e5bf55
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Dawid,
Thanks for your email. It seems StandardQueryParser is free from
this unexpected behavior.

I used the code below with Lucene 6.2.1
(org.apache.lucene.queryparser.classic.QueryParser)

    QueryParser parser =3D new QueryParser("test", new WhitespaceAnalyzer()=
);

    parser.setDefaultOperator(QueryParser.Operator.AND);
    Query query =3D parser.parse("foo AND bar OR baz ");
    System.out.println(query.toString());

    parser.setDefaultOperator(QueryParser.Operator.OR);
    query =3D parser.parse("foo AND bar OR baz ");
    System.out.println(query.toString());


I can also reproduce it on Elasticsearch 2.2 which uses Lucene 5.4.0

$  curl -s 'localhost:9200/test/_search?pretty' -d '{ "query": {
"query_string": { "query": "foo AND bar OR baz" , "default_operator": "and"
} } , "profile" : true}' | grep luce
          "lucene" : "+_all:foo _all:bar _all:baz",
...

$ curl -s 'localhost:9200/test/_search?pretty' -d '{ "query": {
"query_string": { "query": "foo AND bar OR baz" , "default_operator": "or"
} } , "profile" : true}' | grep luce
          "lucene" : "+_all:foo +_all:bar _all:baz",
...

Elasticsearch uses class called MapperQueryParser which extends
org.apache.lucene.queryparser.classic.QueryParser

--
Pawe=C5=82 R=C3=B3g

On Wed, Nov 9, 2016 at 6:10 PM, Dawid Weiss <dawid.weiss@gmail.com> wrote:

> Which Lucene version and which query parser is this? Can you provide a
> test case/ code sample?
> I just tried with StandardQueryParser and for:
>
>         sqp.setDefaultOperator(StandardQueryConfigHandler.Operator.AND);
>         dump(sqp.parse("foo AND bar OR baz", "field_a"));
>         sqp.setDefaultOperator(StandardQueryConfigHandler.Operator.OR);
>         dump(sqp.parse("foo AND bar OR baz", "field_a"));
>
> I get the same result:
>
> BooleanQuery: +field_a:foo +field_a:bar field_a:baz
>
> Dawid
>
> On Wed, Nov 9, 2016 at 6:04 PM, Pawel Rog <ppp.pawelrog@gmail.com> wrote:
> > Hi Eric,
> > Thank you for your email.
> > I understand that Lucene queries are not in boolean logic. My point is
> only
> > that I would expect identical Lucene queries build from the same input
> > string. My intuition says that default operator should not matter in 2
> > examples I presented in previous email.
> >
> > --
> > Pawe=C5=82 R=C3=B3g
> >
> > On Wed, Nov 9, 2016 at 4:32 PM, Erick Erickson <erickerickson@gmail.com=
>
> > wrote:
> >
> >> Lucene queries aren't boolean logic. You can simulate boolean logic by
> >> explicitly parenthesizing, here's an excellent blog on this:
> >>
> >> https://lucidworks.com/blog/why-not-and-or-and-not/
> >>
> >> Best,
> >> Erick
> >>
> >> On Wed, Nov 9, 2016 at 1:37 AM, Pawel Rog <ppp.pawelrog@gmail.com>
> wrote:
> >> > Hello ,
> >> > I have a query `foo AND bar OR baz`. When I use "AND" as a default
> >> operator
> >> > this is the resulting Lucene  query:
> >> >
> >> > `+test:foo test:bar test:baz`
> >> >
> >> > When I use "OR" this is the resulting query
> >> >
> >> > `+test:foo +test:bar test:baz`
> >> >
> >> >
> >> > I expected these two return exactly the same Lucene query because I
> used
> >> > operator explicitly. I thought that the default operator is used onl=
y
> >> when
> >> > operator is not explicitly mentioned in the query. Am I missing
> something
> >> > or this is not expected behavior (bug)?
> >> >
> >> > --
> >> > Pawe=C5=82 R=C3=B3g
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: java-user-help@lucene.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--001a11401dc6902c4a0540e5bf55--