On 4/22/2015 9:27 AM, Dhutia, Devansh wrote:
> I don’t know if that’s completely true, or maybe I’m misunderstanding
> something.
>
> If it doesn’t support purely negative subqueries, this shouldn't work, but
> does:
> q=*:*&fq=(-(field:V1))
It's Lucene that has no support for purely negative
: Subject: Boolean filter query not working as expected
:
: I have an automated filter query builder that uses the SolrNet nuget package
to build out boolean filters. I have a scenario where it is generating a fq in
the following format:
:
: ((-(field:V1) AND -(field:V2)) AND -(field:V3))
: The f
If I upgrade to using the edismax parser in my fq, I get the desired
results.
The default lucene parser on fq must not be able to parse the more complex
nested clauses
q=*:*&fq={!type=edismax}((-(field:V1) AND -(field:V2)) AND -(field:V3)) -
Works
On 4/22/15, 3:27 PM, "Dhutia, Devansh" w
I don’t know if that’s completely true, or maybe I’m misunderstanding
something.
If it doesn’t support purely negative subqueries, this shouldn't work, but
does:
q=*:*&fq=(-(field:V1))
However, for me, the following is a summary of what works & what doesn’t.
q=*:*&fq=(-(field:V1))
A purely negative sub-query is not supported by Lucene - you need to have
at least one positive term, such as "*:*, at each level of sub-query. Try:
((*:* -(field:V1) AND -(field:V2)) AND -(field:V3))
-- Jack Krupansky
On Wed, Apr 22, 2015 at 10:56 AM, Dhutia, Devansh
wrote:
> I have an automa
I have an automated filter query builder that uses the SolrNet nuget package to
build out boolean filters. I have a scenario where it is generating a fq in the
following format:
((-(field:V1) AND -(field:V2)) AND -(field:V3))
The filter looks legal to me (albeit with extra parentheses), but the
