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.pawel...@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 only when > operator is not explicitly mentioned in the query. Am I missing something > or this is not expected behavior (bug)? > > -- > Paweł Róg --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
