# Effect of " index.mapping.total\_fields.limit" on elasticsearch fuctions?

**URL:** <https://discuss.elastic.co/t/effect-of-index-mapping-total-fields-limit-on-elasticsearch-fuctions/118854>\
**Category:** Elasticsearch\
**Created:** [February 7, 2018, 1:53pm UTC](https://discuss.elastic.co/t/effect-of-index-mapping-total-fields-limit-on-elasticsearch-fuctions/118854 "2018-02-07T13:53:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![madhur\_yadav](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@madhur\_yadav](https://discuss.elastic.co/u/madhur_yadav)\
**Post date:** [February 7, 2018, 1:53pm UTC](https://discuss.elastic.co/t/effect-of-index-mapping-total-fields-limit-on-elasticsearch-fuctions/118854/1 "2018-02-07T13:53:17Z")

</div>

Hi there,

currently I'm working on a product which uses Elasticsearch.  
the current `index.mapping.total_fields.limit` is `1000` and due to growing fields in the indexes, I want to increase it upto `5000`.

My question is - Would it impact on Elasticsearch in any way; be it search and retrieval or on previously indexed fields or anything else.

I'm asking this because as the prodcut and log files will increase, I'll be increasing the fields limit, So i just wanted to know the long term effect of this configuration change.

---

<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 7, 2018, 1:53pm UTC](https://discuss.elastic.co/t/effect-of-index-mapping-total-fields-limit-on-elasticsearch-fuctions/118854/2 "2018-03-07T13:53:30Z")

</div>

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