Mind you, I only have 10's of thousands of documents I am aggregating over... maybe the perf difference is negligible?
On Wednesday, 18 June 2014 17:21:26 UTC+1, mooky wrote: > > Hm, Interesting. > I currently make one request that performs multiple aggregations. All my > aggregations have a filter aggregation as the top level item (all are > different). > Do you think it would be better performance executing multiple requests > with a filterQuery instead? > > > > On Wednesday, 18 June 2014 17:09:32 UTC+1, Adrien Grand wrote: >> >> Indeed SearchType.COUNT would work great as it would ensure that a single >> round-trip is performed. Other than that, if you want to filter content on >> which you want to aggregate, make sure to put it in a filtered query as >> opposed to a filter aggregation: since aggregations are executed on every >> matching document, this would evaluate the filter against every document >> (since the default query, match_all, matches them all) while if you put the >> filter in the query, elasticsearch would be able to quickly skip over >> non-matching documents. >> > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c70ebe3-2dcc-4882-bfe3-effa6bbfdb48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
