# Finding high cardinality fields

**URL:** <https://discuss.elastic.co/t/finding-high-cardinality-fields/14482>\
**Category:** Elasticsearch\
**Created:** [November 20, 2013, 7:20am UTC](https://discuss.elastic.co/t/finding-high-cardinality-fields/14482 "2013-11-20T07:20:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramchandra\_Phadake](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@Ramchandra\_Phadake](https://discuss.elastic.co/u/Ramchandra_Phadake)\
**Post date:** [November 20, 2013, 7:20am UTC](https://discuss.elastic.co/t/finding-high-cardinality-fields/14482/1 "2013-11-20T07:20:35Z")

</div>

Hi,

We have bunch of high cardinality fields and doing facets on them is very  
expensive. So trying to find ways to prevent end-user from fetching facets  
over those fields.

Meaning we are fine running some nightly jobs to figure out which are high  
cardinality fields.  
One approach is use of term facet query with large size value.then getting  
the size of facet list to get count of unique terms.

Are other approaches to get count of unique terms in a field using facet.  
e.g. kind of count query without returning any facets.

Thanks,  
Ram

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:06am UTC](https://discuss.elastic.co/t/finding-high-cardinality-fields/14482/2 "2017-07-06T02:06:06Z")

</div>

Closed on July 6, 2017, 2:06am UTC


