Hi, thanks for your help, I figued it out myself I guess.
All parts of an fq are always intersected, so it has no effect to put
a boolean operator inside a fq like in
fq=+tags:(Gucci) OR -tags:(watch sunglasses)
(would be a mildly strange query anyway)
The order in which the intersections are made follows their appearance
in the query I suppose.
best regards,
Alex
On Di, 2010-04-27 at 12:09 -0700, Chris Hostetter wrote:
> : i was wondering how the following query might be processed:
> :
> : ?q=*:*&fq=+tags:(Gucci)&fq=-tags:(watch sunglasses)
>
> they are intersected so only documents matching all of them are potential
> matches.
>
> : and if there is a difference to a query with only one fq parameter like
> :
> : ?q=*:*&fq=+tags:(Gucci) -tags:(watch sunglasses)
> :
> : I am aware of the chaching implications but i am not sure how the set
> : intersections work between the results of the 'q' and one or more 'fq'
> : parameters and if it is possible to use boolean operators inside a
> : filter query.
>
> filter queries an use an QParser, so you can use boolean operators if the
> QParser supports it (by default the QParser is "lucene" so "yes") ...
>
> i don't understand the "i am not sure how the set intersections work between
> the results of the 'q' and one or more 'fq'" part of your question, can
> you clarify what it is you are asking?
>
>
> -Hoss
>
|