Re: How are (multiple) filter queries processed?

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 m

Re: How are (multiple) filter queries processed?

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 m

Re: How are (multiple) filter queries processed?

: 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=+tag

How are (multiple) filter queries processed?

Hi, i was wondering how the following query might be processed: ?q=*:*&fq=+tags:(Gucci)&fq=-tags:(watch sunglasses) 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