# Problem cardinality and date\_histogram

**URL:** <https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437>\
**Category:** Elasticsearch\
**Created:** [June 30, 2016, 3:55pm UTC](https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437 "2016-06-30T15:55:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mathieu\_Lardeaux](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@Mathieu\_Lardeaux](https://discuss.elastic.co/u/Mathieu_Lardeaux)\
**Post date:** [June 30, 2016, 3:55pm UTC](https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437/1 "2016-06-30T15:55:09Z")

</div>

Hello all,

I have a problem for a answer Elastic Search.

I have 65 doc\_count after request done and cardinality give 67 doc\_count...

Answer :

```auto
"aggregations": {
    "xxxxxxx": {
      "buckets": [
        {
          "key_as_string": "xxxxxxxx",
          "key":xxxxxxxx,
          "doc_count": 65,
          "xxxxx": {
            "doc_count_error_upper_bound": 0,
            "sum_other_doc_count": 0,
            "buckets": [
              {
                "key": "xxxxxx",
                "doc_count": 63,
                "distinct": {
                  "value": 67
                }
              },
              {
                "key": "xxxxx",
                "doc_count": 2,
                "distinct": {
                  "value": 2
                }
              }
            ]
          }
        }
      ]
    }
  }

```

Thanks all 🙂

---

<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:** [June 30, 2016, 5:28pm UTC](https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437/2 "2016-06-30T17:28:39Z")

</div>

The cardinality aggregation returns approximate counts. In your case, the cardinality agg is below 2 levels of bucket aggregations, so it picks a rather low precision threshold in order to avoid causing out-of-memory errors. You could set a higher `precision_threshold` in order to get some precision back but note that it might cause out-of-memory issues if the parent aggregations create many buckets.

---

<div class="post-metadata">

**Author:** ![Mathieu\_Lardeaux](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@Mathieu\_Lardeaux](https://discuss.elastic.co/u/Mathieu_Lardeaux)\
**Post date:** [July 1, 2016, 8:52am UTC](https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437/3 "2016-07-01T08:52:10Z")

</div>

Thanks for the answer.

---

<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:** [July 5, 2017, 10:38pm UTC](https://discuss.elastic.co/t/problem-cardinality-and-date-histogram/54437/4 "2017-07-05T22:38:59Z")

</div>