I'm a bit confused, is terms filter slower because it has to iterate
through a list of bitsets whereas lucene already has access to the list of
matching documents via inverted index?
Also, if I set cache=true for each individual filter, does it allow me to
create any permutation of my bool filter
With term queries I imagine its nanoseconds to a net loss to use the filter
cache. You should really test it though because I'm not 100% sure.
There was talk of elassticsearch being more intelligent about which filters
it decides to cache but I don't know where that's gone.
Nik
On Wed, Apr 22, 2
In terms of performance, we we talking nanoseconds saved by using term
filters, or possibly a few milliseconds? Given the performance requirements
for this query, even saving a few milliseconds is a lot. Also, it looks
like I should cache at the individual filter level, as they will be bundled
diff
On Wed, Apr 22, 2015 at 2:41 PM, Ed Kim wrote:
> Hi, I have a dynamic query built via java api that assembles a filtered
> query depending on the parameter input. I have about a dozen filters
> (mostly term filters) that may or may not be used, and had a couple
> questions:
>
> 1. Is it ok to sim
Hi, I have a dynamic query built via java api that assembles a filtered
query depending on the parameter input. I have about a dozen filters
(mostly term filters) that may or may not be used, and had a couple
questions:
1. Is it ok to simply set the parent boolFilterBuilder cache setting to
tr
