# Limit of total fields \[1000\] in index exceeded

**URL:** <https://discuss.elastic.co/t/limit-of-total-fields-1000-in-index-exceeded/295093>\
**Category:** Elasticsearch\
**Created:** [January 21, 2022, 6:33pm UTC](https://discuss.elastic.co/t/limit-of-total-fields-1000-in-index-exceeded/295093 "2022-01-21T18:33:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![galion96](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/galion96/32/100699_2.png) [@galion96](https://discuss.elastic.co/u/galion96)\
**Post date:** [January 21, 2022, 6:33pm UTC](https://discuss.elastic.co/t/limit-of-total-fields-1000-in-index-exceeded/295093/1 "2022-01-21T18:33:11Z")

</div>

Hello,  
I saw that there are some concerns to raising the total limit on fields above 1000.  
I have a situation where I am not sure how to approach it from the design point of view.  
I lots simple key value pairs: key1:15, key2:45, key99999:1313123.  
Where as if a certain document receives a key it gets sorted by the value.

I ended up creating an object and just put the key value pairs inside so I can match it easy.  
For example I have sorting: "object.key".

I was wondering if I just use a simple object with bunch of strings inside that are just there for exact matching should I worry about raising this limit to 10k, or 20k

---

<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:** [February 18, 2022, 6:33pm UTC](https://discuss.elastic.co/t/limit-of-total-fields-1000-in-index-exceeded/295093/2 "2022-02-18T18:33:39Z")

</div>

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