# Alternate approach for exceeding fields \>1000

**URL:** <https://discuss.elastic.co/t/alternate-approach-for-exceeding-fields-1000/146159>\
**Category:** Elasticsearch\
**Created:** [August 27, 2018, 11:01am UTC](https://discuss.elastic.co/t/alternate-approach-for-exceeding-fields-1000/146159 "2018-08-27T11:01:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![muthucse](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/muthucse/32/45217_2.png) [@muthucse](https://discuss.elastic.co/u/muthucse)\
**Post date:** [August 27, 2018, 11:01am UTC](https://discuss.elastic.co/t/alternate-approach-for-exceeding-fields-1000/146159/1 "2018-08-27T11:01:46Z")

</div>

We have index with more than 1000 fields with parent and child approach. Is it good to exceed more than 1000 fields. parent with 500 fields and child with 600 fields in a same index ?

Is it good to increase the default limit with the above approach ?

---

<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:** [September 24, 2018, 11:02am UTC](https://discuss.elastic.co/t/alternate-approach-for-exceeding-fields-1000/146159/2 "2018-09-24T11:02:03Z")

</div>

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