Hi,
Chris Hostetter wrote:
AND, OR, and NOT are just syntactic-sugar for modifying
the MUST, MUST_NOT, and SHOULD. The default op of "OR" only affects the
first clause of your query (R) because it doesn't have any modifiers --
Thanks for pointing that out!
-Sascha
the second clause has that
: thanks for your explanations. But why are all docs being *removed* from the
: set of all docs that contain R in their topic field? This would correspond to
: a boolean AND and would stand in conflict with the clause q.op=OR. This seems
: a bit strange to me.
Erick's explanation might have been
Hi Erick,
thanks for your explanations. But why are all docs being *removed* from
the set of all docs that contain R in their topic field? This would
correspond to a boolean AND and would stand in conflict with the clause
q.op=OR. This seems a bit strange to me.
Furthermore, Smiley & Pugh st
This may help:
http://lucene.apache.org/java/2_4_0/queryparsersyntax.html#Boolean%20operators
But the clause you specified translates roughly as "find all the
documents that contain R, then remove any of them that match
"* TO *". * TO * contains all the documents with R, so everything
you just mat
Hi Ahmet,
it works, thanks a lot!
To be true I have no idea what's the problem with
defType=lucene&q.op=OR&df=topic&q=R NOT [* TO *]
-Sascha
Ahmet Arslan wrote:
I have a (multi-valued) field topic in my index which does
not need to exist in every document. Now, I'm struggling
with formulating
> I have a (multi-valued) field topic in my index which does
> not need to exist in every document. Now, I'm struggling
> with formulating a query that returns all documents that
> either have no topic field at all *or* whose topic field
> value is R.
Does this work?
&defType=lucene&q.op=OR&q=topi
