Thank you Dawid :)
--
Paweł Róg
On Thu, Nov 10, 2016 at 1:30 PM, Dawid Weiss wrote:
> This does look odd. I filed this issue to track it:
>
> https://issues.apache.org/jira/browse/LUCENE-7550
>
> But I can't promise you I'll have the time to look into this any time
> soon. Feel free to step dow
This does look odd. I filed this issue to track it:
https://issues.apache.org/jira/browse/LUCENE-7550
But I can't promise you I'll have the time to look into this any time
soon. Feel free to step down through the source and see why the
difference is there (patches welcome!).
On Wed, Nov 9, 2016
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 = new QueryParser("test", new WhitespaceAnalyzer());
parser.setDefaultOperat
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.setDefaultOpe
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.
--
Pa
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 wrote:
> Hello ,
> I have a query `foo AND bar OR baz`. W
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
