# How to set EagerGlobalOrdinals flag for parent-child join field in Nest

**URL:** <https://discuss.elastic.co/t/how-to-set-eagerglobalordinals-flag-for-parent-child-join-field-in-nest/130148>\
**Category:** Elasticsearch\
**Created:** [May 1, 2018, 7:15pm UTC](https://discuss.elastic.co/t/how-to-set-eagerglobalordinals-flag-for-parent-child-join-field-in-nest/130148 "2018-05-01T19:15:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ttonyyao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ttonyyao/32/30654_2.png) [@ttonyyao](https://discuss.elastic.co/u/ttonyyao)\
**Post date:** [May 1, 2018, 7:15pm UTC](https://discuss.elastic.co/t/how-to-set-eagerglobalordinals-flag-for-parent-child-join-field-in-nest/130148/1 "2018-05-01T19:15:51Z")

</div>

Looks like the **join attribute** do not have the **EagerGlobalOrdinals** flag while Keyword and Text have it.

The flag is import to tune the performance. I can manually build json request to change the join field mapping. However, I still want to know how to do it using the auto mapping attributes.

---

<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:** [May 29, 2018, 7:15pm UTC](https://discuss.elastic.co/t/how-to-set-eagerglobalordinals-flag-for-parent-child-join-field-in-nest/130148/2 "2018-05-29T19:15:53Z")

</div>

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