# Term aggregation shard level aggreagation issue

**URL:** https://discuss.elastic.co/t/term-aggregation-shard-level-aggreagation-issue/113493
**Category:** Elasticsearch
**Created:** [December 28, 2017, 6:44pm UTC](https://discuss.elastic.co/t/term-aggregation-shard-level-aggreagation-issue/113493 "2017-12-28T18:44:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ankur\_singla](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankur_singla/32/45612_2.png) [@ankur\_singla](https://discuss.elastic.co/u/ankur_singla)
#### Post date: [December 28, 2017, 6:44pm UTC](https://discuss.elastic.co/t/term-aggregation-shard-level-aggreagation-issue/113493/1 "2017-12-28T18:44:21Z")

</div>

As explained in documentation term aggregation can't be correct as internally elastic search using shard level aggregation. is there any way to ensure that this issue should not comes up.

---

<div class="post-metadata">

### Author: ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)
#### Post date: [December 29, 2017, 8:37am UTC](https://discuss.elastic.co/t/term-aggregation-shard-level-aggreagation-issue/113493/2 "2017-12-29T08:37:27Z")

</div>

No, but you can check the error bounds in the response to know how off counts are.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 26, 2018, 8:37am UTC](https://discuss.elastic.co/t/term-aggregation-shard-level-aggreagation-issue/113493/3 "2018-01-26T08:37:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
