# Best approach between increasing index properties size or large no of nested document

**URL:** <https://discuss.elastic.co/t/best-approach-between-increasing-index-properties-size-or-large-no-of-nested-document/21363>\
**Category:** Elasticsearch\
**Created:** [December 23, 2014, 6:22am UTC](https://discuss.elastic.co/t/best-approach-between-increasing-index-properties-size-or-large-no-of-nested-document/21363 "2014-12-23T06:22:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandeep\_kaushal\_verm](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@sandeep\_kaushal\_verm](https://discuss.elastic.co/u/sandeep_kaushal_verm)\
**Post date:** [December 23, 2014, 6:22am UTC](https://discuss.elastic.co/t/best-approach-between-increasing-index-properties-size-or-large-no-of-nested-document/21363/1 "2014-12-23T06:22:22Z")

</div>

I have a user document

User has n properties of his own which is around 200.  
User has few nested properties like his activities, products, brands etc.

Case I,  
If I put all data in flat way, not creating any nested objects, it  
increases index properties size to around 50K.

Case II,  
If I put all data in nested objects, it increases no of Document to around  
300 per user. In this case total documents grows in billions.

Case III,  
If I take mixed approach, It will make index properties size of around 500  
and few nested objects. Here document size of user is around 45.

I have to take decision on choosing best way on above.

I appreciate if you suggest any other way which is appropriate in my  
situation.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/98d38b20-3645-48a7-98ea-385f186c3c90%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/98d38b20-3645-48a7-98ea-385f186c3c90%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![sandeep\_kaushal\_verm](https://avatars.discourse-cdn.com/v4/letter/s/4491bb/32.png) [@sandeep\_kaushal\_verm](https://discuss.elastic.co/u/sandeep_kaushal_verm)\
**Post date:** [December 27, 2014, 12:57pm UTC](https://discuss.elastic.co/t/best-approach-between-increasing-index-properties-size-or-large-no-of-nested-document/21363/2 "2014-12-27T12:57:34Z")

</div>

hh

On Tuesday, 23 December 2014 11:52:22 UTC+5:30, sandeep kaushal verma wrote:

> I have a user document
> 
> User has n properties of his own which is around 200.  
> User has few nested properties like his activities, products, brands etc.
> 
> Case I,  
> If I put all data in flat way, not creating any nested objects, it  
> increases index properties size to around 50K.
> 
> Case II,  
> If I put all data in nested objects, it increases no of Document to  
> around 300 per user. In this case total documents grows in billions.
> 
> Case III,  
> If I take mixed approach, It will make index properties size of around 500  
> and few nested objects. Here document size of user is around 45.
> 
> I have to take decision on choosing best way on above.
> 
> I appreciate if you suggest any other way which is appropriate in my  
> situation.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/e1903fdf-3e5c-4228-994a-945ea7001e4d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/e1903fdf-3e5c-4228-994a-945ea7001e4d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:41am UTC](https://discuss.elastic.co/t/best-approach-between-increasing-index-properties-size-or-large-no-of-nested-document/21363/3 "2017-07-06T00:41:50Z")

</div>


