Filters vs Queries


(Chris Berkhout) #1

Hi everyone,

The choice between filters and regular 'must' query conditions is
basically about performance, right?

Because filters can be cached better and don't do scoring.

I'm using the Tire gem, but apparently it doesn't do multiple filters
at the moment, so I'm thinking of making them regular boolean
conditions for now.

Cheers,
Chris


(Clinton Gormley) #2

HI Chris

The choice between filters and regular 'must' query conditions is
basically about performance, right?

Because filters can be cached better and don't do scoring.

Correct

I'm using the Tire gem, but apparently it doesn't do multiple filters
at the moment, so I'm thinking of making them regular boolean
conditions for now.

I don't know the API of the Tire gem, but you should be able to combine
multiple filters using the and|or|not filters (in a similar way to the
bool query/filter)

clint


(Chris Berkhout) #3

Thanks Clint!

On Tue, Oct 11, 2011 at 5:20 PM, Clinton Gormley clint@traveljury.com wrote:

HI Chris

The choice between filters and regular 'must' query conditions is
basically about performance, right?

Because filters can be cached better and don't do scoring.

Correct

I'm using the Tire gem, but apparently it doesn't do multiple filters
at the moment, so I'm thinking of making them regular boolean
conditions for now.

I don't know the API of the Tire gem, but you should be able to combine
multiple filters using the and|or|not filters (in a similar way to the
bool query/filter)

clint


(system) #4