: Solr can process the query which has NOT operator ("-") in the head.
: If Solr find it, Solr adds MatchAllDocsQuery automatically
: in the front of that query as follows:
thta's not strictly true ... Solr doesn't *add* a MatchAllDocsQuery if the
query is entirely prohibitive, instead Solr execu
On 12-Jul-07, at 6:25 PM, Lance Lance wrote:
A simplified version of the problem:
text -(collection:pile1)
works, while
text (-collection:pile1)
finds zero records.
see my other message. You cannot create a (sub)query with only
prohibited clauses. The second query asks:
Q = find docs
A simplified version of the problem:
text -(collection:pile1)
works, while
text (-collection:pile1)
finds zero records.
lance
_
From: Lance Lance [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 12, 2007 5:58 PM
To: 'solr-user@lucene.apache.org'
Subject: Questio
Lance,
I think you are right. I met the same problem before.
> -(collection:pile1 OR collection:pile2)
Solr can process the query which has NOT operator ("-") in the head.
If Solr find it, Solr adds MatchAllDocsQuery automatically
in the front of that query as follows:
MatchAllDocsQuery -(coll
Ok, here's a simpler version:
_
From: Lance Lance [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 12, 2007 5:58 PM
To: 'solr-user@lucene.apache.org'
Subject: Question on query syntax
Are there any known bugs in the syntax parser? We're using lucene-2.2.0 and
On 12-Jul-07, at 5:58 PM, Lance Lance wrote:
Are there any known bugs in the syntax parser? We're using
lucene-2.2.0 and
Solr 1.2.
We have documents with searchable text and a field 'collection'.
This query works as expected, finding everything except for
collections
'pile1' and 'pile2'.
Are there any known bugs in the syntax parser? We're using lucene-2.2.0 and
Solr 1.2.
We have documents with searchable text and a field 'collection'.
This query works as expected, finding everything except for collections
'pile1' and 'pile2'.
text -(collection:pile1 OR collection:pile2)
