# Return document for aggregation result

**URL:** <https://discuss.elastic.co/t/return-document-for-aggregation-result/85510>\
**Category:** Elasticsearch\
**Created:** [May 12, 2017, 7:21am UTC](https://discuss.elastic.co/t/return-document-for-aggregation-result/85510 "2017-05-12T07:21:52Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [May 12, 2017, 2:20pm UTC](https://discuss.elastic.co/t/return-document-for-aggregation-result/85510/6 "2017-05-12T14:20:20Z")

</div>

> [@animageofmine](#):
>
> I thought that elasticsearch keeps additional metadata for each shard like memsql does, especially for min/max values.

Max agg is designed for use in a context which would prevent it from making use of any such pre-computed global max values - see [Very slow aggregation performance for trivial aggs - #2 by Mark\_Harwood](https://discuss.elastic.co/t/very-slow-aggregation-performance-for-trivial-aggs/24964/2)

---

_[View the full topic](https://discuss.elastic.co/t/return-document-for-aggregation-result/85510)._