<p dir="auto"><strong>Describe the feature</strong>:<br>
currently term aggregation execute below: the node coordinating the search process will request each shard to provide its own top size term buckets and once all shards respond, it will reduce the results to the final list that will then be returned to the client.<br>
if try to get all terms agg, it will cause memory issue.<br>
this request is below:<br>
not based on top size term but top term on each shard's term dictionary and return the agg. maintain a context for iteration to traverse all terms and get exact results.</p>
<p dir="auto">Terms aggregation  does not support a way to page through the buckets returned.<br>
To work around this, I've been trying to set 'min_doc_count'  to limit the buckets returned and using a 'exclude' filter, to exclude already 'seen' pages.</p>
<p dir="auto">Will this result in better running time performance on the ES cluster as compared to getting all the buckets and then doing my own paging logic client side ?</p>