# How to deal with nested fields limit

**URL:** <https://discuss.elastic.co/t/how-to-deal-with-nested-fields-limit/163544>\
**Category:** Elasticsearch\
**Created:** [January 9, 2019, 1:52pm UTC](https://discuss.elastic.co/t/how-to-deal-with-nested-fields-limit/163544 "2019-01-09T13:52:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [January 9, 2019, 2:08pm UTC](https://discuss.elastic.co/t/how-to-deal-with-nested-fields-limit/163544/2 "2019-01-09T14:08:05Z")

</div>

> [@alex\_b](#):
>
> I probably have a wrong understanding of the nested\_fields.limit.

It's a limit on the number of fields declared in the mapping as type `nested` - not the number of array elements you choose to add as values for any of those fields

> [@alex\_b](#):
>
> what is the recommended strategy for the case, that one have objects containing arrays

See [this flowchart](https://discuss.elastic.co/t/indexing-hierarchical-couchbase-documents/70400/2) to help decide. You shouldn't need nested if you only search on single fields at a time - it's when you AND properties from 2 different fields that the "cross-matching" problem occurs and you need to reach for `nested` to make the objects different matchable entities.

---

_[View the full topic](https://discuss.elastic.co/t/how-to-deal-with-nested-fields-limit/163544)._