# How many fields should be fine for ES?

**URL:** <https://discuss.elastic.co/t/how-many-fields-should-be-fine-for-es/80663>\
**Category:** Elasticsearch\
**Created:** [March 30, 2017, 11:29am UTC](https://discuss.elastic.co/t/how-many-fields-should-be-fine-for-es/80663 "2017-03-30T11:29:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielwalker](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielwalker/32/14396_2.png) [@danielwalker](https://discuss.elastic.co/u/danielwalker)\
**Post date:** [March 30, 2017, 11:29am UTC](https://discuss.elastic.co/t/how-many-fields-should-be-fine-for-es/80663/1 "2017-03-30T11:29:20Z")

</div>

Hi guys,

I am using elasticsearch php api for creating index with some fields.

If I add new fields, I need to refresh the fields list in Kibana, which is OK for me.

But what is the maximum amount of fields for ES, or how many fields are tuned for Elasticsearch? If I add many fields, is this wasting resources?

---

<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:** [March 31, 2017, 8:18am UTC](https://discuss.elastic.co/t/how-many-fields-should-be-fine-for-es/80663/2 "2017-03-31T08:18:26Z")

</div>

Historically when people have had issues with clusters it has been with several million fields.  
It's best to avoid these levels of unique field names.

---

<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:** [April 28, 2017, 8:18am UTC](https://discuss.elastic.co/t/how-many-fields-should-be-fine-for-es/80663/3 "2017-04-28T08:18:35Z")

</div>

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