# Designing an Index with high Cardinality for a field distributed across multiple shards

**URL:** <https://discuss.elastic.co/t/designing-an-index-with-high-cardinality-for-a-field-distributed-across-multiple-shards/374302>\
**Category:** Elasticsearch\
**Created:** [February 10, 2025, 10:13am UTC](https://discuss.elastic.co/t/designing-an-index-with-high-cardinality-for-a-field-distributed-across-multiple-shards/374302 "2025-02-10T10:13:44Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [February 13, 2025, 9:42am UTC](https://discuss.elastic.co/t/designing-an-index-with-high-cardinality-for-a-field-distributed-across-multiple-shards/374302/5 "2025-02-13T09:42:06Z")

</div>

Oh I see, sorry about that! I thought the question was about index design and missed the Kibana requirement ☹

Some alternatives for this have been discussed [here](https://discuss.elastic.co/t/how-to-analyse-nested-fields/325944/2) - basically using a flattened structure, or using a custom Vega visualization over a nested query.

---

_[View the full topic](https://discuss.elastic.co/t/designing-an-index-with-high-cardinality-for-a-field-distributed-across-multiple-shards/374302)._