Yes, it SHOULD! And in the LucidWorks Search query parser it does. Why
doesn't it in Solr? Ask Yonik to explain that!
-- Jack Krupansky
-Original Message-
From: Rahul R
Sent: Friday, June 07, 2013 1:21 AM
To: solr-user@lucene.apache.org
Subject: Re: OR query with null value and non
: Rahul R
Sent: Friday, June 07, 2013 1:21 AM
To: solr-user@lucene.apache.org
Subject: Re: OR query with null value and non-null value(s)
Thank you Shawn. This does work. To help me understand better, why do
we need the *:* ? Shouldn't it be implicit ?
Shouldn't
fq=(price:4+OR+(-price
I have recently enabled facet.missing=true in solrconfig.xml which gives
null facet values also. As I understand it, the syntax to do a faceted
search on a null value is something like this:
fq=-price:[* TO *]
So when I want to search on a particular value (for example : 4) OR null
value, I would
On 6/6/2013 12:28 PM, Rahul R wrote:
I have recently enabled facet.missing=true in solrconfig.xml which gives
null facet values also. As I understand it, the syntax to do a faceted
search on a null value is something like this:
fq=-price:[* TO *]
So when I want to search on a particular value
Thank you Shawn. This does work. To help me understand better, why do
we need the *:* ? Shouldn't it be implicit ?
Shouldn't
fq=(price:4+OR+(-price:[* TO *])) //does not work
mean the same as
fq=(price:4+OR+(*:* -price:[* TO *])) //works
Why does Solr need the *:* there ?
On Fri, Jun
On 6/6/2013 11:21 PM, Rahul R wrote:
Thank you Shawn. This does work. To help me understand better, why do
we need the *:* ? Shouldn't it be implicit ?
Shouldn't
fq=(price:4+OR+(-price:[* TO *])) //does not work
mean the same as
fq=(price:4+OR+(*:* -price:[* TO *])) //works
Why
