I think this is the issue with top-level negative clause. Lucene does
not know what "-x" means without "*:* -x" to establish the baseline
set to subtract from. Solr has a workaround for top-level negative
query, so "-WithinPrefixTreeQuery..." triggers that special treatment.
But
Hi Alex and Erick,
We could possibly put them in fq, but how we set everything up would make
it hard to do so, but going that route might be the only option.
I did take a look at the parsed query and this is the difference:
This is the one that works:
Also, Solr does _not_ implement strict Boolean logic, although with
appropriate parentheses you can get it to look like Boolean logic.
See: https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
Additionally, for _some_ clauses a pure-not query is translated into
*:* -pure_not_query which is
Have a look at what debug shows in the parsed query. I think every
bracket is quite significant actually and you are generating a
different type of clause.
Also, have you thought about putting those individual clauses into
'fq' instead of jointly into 'q'? This may give you faster search too,
as
Hi,
I am doing some date queries and I was wondering if there is some way of
getting this query to work.
( ( !{!field f=collection_date_range op=Within v='[2000-01-01 TO
2018-09-18]'} AND !{!field f=collection_date_range op=Within v='[1960-01-01
TO 1998-09-18]'} ) AND collection_season:([1999-05
