# ElasticSearch mapping & cluster\_state

**URL:** <https://discuss.elastic.co/t/elasticsearch-mapping-cluster-state/121465>\
**Category:** Elasticsearch\
**Created:** [February 26, 2018, 10:15am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-cluster-state/121465 "2018-02-26T10:15:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mjunaidmuzammil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mjunaidmuzammil/32/56910_2.png) [@mjunaidmuzammil](https://discuss.elastic.co/u/mjunaidmuzammil)\
**Post date:** [February 26, 2018, 10:15am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-cluster-state/121465/1 "2018-02-26T10:15:27Z")

</div>

Hi,

One of the problems that we often hear with the elasticsearch community is huge **cluster\_state**. From my prior experience, I have noticed that in majority of the cases too many mapping field definitions is the cause of the problem. For one of our use case, we have plethora of different fields present in our JSON document.

Obviously we don't want each of them to be indexed, but non-indexed fields are also present in **cluster\_state**. Is there a way to mask out these non-indexed fields from **cluster\_state**?

---

<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:** [March 26, 2018, 10:15am UTC](https://discuss.elastic.co/t/elasticsearch-mapping-cluster-state/121465/2 "2018-03-26T10:15:33Z")

</div>

Closed on March 26, 2018, 10:15am UTC

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