lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Otis Gospodnetic <otis_gospodne...@yahoo.com>
Subject Re: Unexpected boolean query behavior
Date Thu, 14 Jan 2010 19:42:46 GMT
Mark,

Does it help if you rewrite your query using +/- syntax ("required", "prohibited"), or nothing
for "should"?  Because that's what happens under the hood (terms are required, prohibited,
or should occur).


Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch



----- Original Message ----
> From: markwaddle <mark@markwaddle.com>
> To: solr-user@lucene.apache.org
> Sent: Thu, January 14, 2010 2:39:21 PM
> Subject: Unexpected boolean query behavior
> 
> 
> Here is my query:
> (virt* AND "machine fingerprinting") OR (virt* AND encryption) OR (virt* AND
> anonymous) OR (virt* AND analytic*) AND owned:true
> 
> It can be broken down to:
> (A) OR (B) OR (C) OR (D) AND E
> 
> A, B, C and D are themselves AND boolean clauses.
> 
> The E clause at the end is not behaving the way I would expect. No matter
> how I order the A,B,C and D clauses, it always returns the equivalent of
> ((D) AND E).
> 
> When I add additional parentheses it behaves the way I expect. Like:
> ((A) OR (B) OR (C) OR (D)) AND E
> or
> (A) OR (B) OR (C) OR ((D) AND E)
> 
> Can anyone explain why it behaves the way it does without the parentheses?
> Is there something I am missing in the way it processes boolean clauses?
> 
> Thanks,
> Mark
> -- 
> View this message in context: 
> http://old.nabble.com/Unexpected-boolean-query-behavior-tp27166967p27166967.html
> Sent from the Solr - User mailing list archive at Nabble.com.


Mime
View raw message