# Performance of has\_child query for document with large text

**URL:** <https://discuss.elastic.co/t/performance-of-has-child-query-for-document-with-large-text/41467>\
**Category:** Elasticsearch\
**Created:** [February 11, 2016, 10:12am UTC](https://discuss.elastic.co/t/performance-of-has-child-query-for-document-with-large-text/41467 "2016-02-11T10:12:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gian\_Maria\_Ricci](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gian_maria_ricci/32/1377_2.png) [@Gian\_Maria\_Ricci](https://discuss.elastic.co/u/Gian_Maria_Ricci)\
**Post date:** [February 11, 2016, 10:12am UTC](https://discuss.elastic.co/t/performance-of-has-child-query-for-document-with-large-text/41467/1 "2016-02-11T10:12:31Z")

</div>

I have this situation, documents have some fields with lots of text that does not change often, and a lot of other fields (used for filtering, faceting, etc that changes often).

Now whenever I need to change one of these properties, I need to reindex the whole document in ES, thus asking ES to parse again the same text data.

One possible solution is storing the fields with lots of text in child object, and issue query with has\_child (ES 1.7). With such scenario I'll reindex the text only when the text changes.

I'm curious if anyone has tested loss of performance when it comes the time to query adopting this solution.

Gian Maria.

---

<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 5, 2017, 11:17pm UTC](https://discuss.elastic.co/t/performance-of-has-child-query-for-document-with-large-text/41467/2 "2017-07-05T23:17:14Z")

</div>

Closed on July 5, 2017, 11:17pm UTC