# Bug in aggregation result when using shards

**URL:** <https://discuss.elastic.co/t/bug-in-aggregation-result-when-using-shards/164161>\
**Category:** Elasticsearch\
**Created:** [January 14, 2019, 2:59pm UTC](https://discuss.elastic.co/t/bug-in-aggregation-result-when-using-shards/164161 "2019-01-14T14:59:49Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [January 14, 2019, 3:42pm UTC](https://discuss.elastic.co/t/bug-in-aggregation-result-when-using-shards/164161/2 "2019-01-14T15:42:29Z")

</div>

Some of the aggregations in Elasticsearch are approximate, and [this includes the terms aggregation](https://www.elastic.co/guide/en/elasticsearch/reference/6.5/search-aggregations-bucket-terms-aggregation.html#search-aggregations-bucket-terms-aggregation-approximate-counts). This trade-off has been made in order to be able to aggregate large data volumes fast, and the reason behind this is explained quite well in [this post](https://discuss.elastic.co/t/background-count-in-significant-terms-not-consistent/55824/8).

---

_[View the full topic](https://discuss.elastic.co/t/bug-in-aggregation-result-when-using-shards/164161)._