# Queries regarding precision\_threshold setting in cardinality aggregation

**URL:** <https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258>\
**Category:** Elasticsearch\
**Created:** [October 20, 2018, 11:38pm UTC](https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258 "2018-10-20T23:38:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shailesh\_Vaidya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shailesh_vaidya/32/24144_2.png) [@Shailesh\_Vaidya](https://discuss.elastic.co/u/Shailesh_Vaidya)\
**Post date:** [October 20, 2018, 11:38pm UTC](https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258/1 "2018-10-20T23:38:09Z")

</div>

Hello,

We are using cardinality aggregation in our project. We have around 1400000 documents each document consist filed named url. I want to count unique url wise document count. Hence I am using term aggregation along with cardinality. However I observed that count is not correct. From ELK documentation we can set precision\_threshold to 40000 at max. Does that mean if unique count is more that 40000 then elastic query results will be in accurate. Could you please confirm.

---

<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:** [October 21, 2018, 7:45am UTC](https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258/2 "2018-10-21T07:45:56Z")

</div>

> [@Shailesh\_Vaidya](#):
>
> query results will be in accurate

Yes. But do you need the cardinality agg in this case? If you want to count hits on urls (assuming docs are web access logs) a terms agg will suffice. Only if you’re doing something like counting unique users per url would you need to also use the cardinality agg on something like the sessionid field

---

<div class="post-metadata">

**Author:** ![Shailesh\_Vaidya](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shailesh_vaidya/32/24144_2.png) [@Shailesh\_Vaidya](https://discuss.elastic.co/u/Shailesh_Vaidya)\
**Post date:** [October 27, 2018, 10:31pm UTC](https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258/3 "2018-10-27T22:31:39Z")

</div>

Hi Mark,

Thanks for reply.

Document consist of Jenkins Build Details. Like URL, Build Number, pipeline-id,repo url etc.  
Basically for each Jenkins build document is created. WIth each build we are also storing department name. Now using Elastic Query we want to extract department wise unique pipeline-urls.

As per your suggestion, we can use cardinality on pipeline-id filed also. However I guess issues will still remain then same. Is there any better way to achieve this.

---

<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:** [November 24, 2018, 10:31pm UTC](https://discuss.elastic.co/t/queries-regarding-precision-threshold-setting-in-cardinality-aggregation/153258/4 "2018-11-24T22:31:40Z")

</div>

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