Optimize sub-aggregations when index is routed by primary bucket aggregation

I'm not sure if anything like this is in place already, but when documents
are routed by a given field that is later used as a primary bucket
aggregation, all data for sub-aggregations will be shard local. It could
be beneficial to take advantage of that locality. Has anyone explored or
considered this?

--
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 elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/565a3aca-4c49-4b78-a4d3-d68e84caa13f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.