# Global Ordinals execution hint
**URL:** https://discuss.elastic.co/t/global-ordinals-execution-hint/289699
**Category:** Elasticsearch
**Created:** [November 19, 2021, 2:42pm UTC](https://discuss.elastic.co/t/global-ordinals-execution-hint/289699 "2021-11-19T14:42:30Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@ananth](https://discuss.elastic.co/u/ananth)
#### Post date: [November 19, 2021, 2:42pm UTC](https://discuss.elastic.co/t/global-ordinals-execution-hint/289699/1 "2021-11-19T14:42:30Z")
Hi All,
I went through all the global ordinal related blogs and previous questions such as
# [Global ordinals performance and size on-heap](https://discuss.elastic.co/t/global-ordinals-performance-and-size-on-heap/158320)"
Whether execution\_hint = map will operate in segment-private ordinal space ?
My understanding is execution\_hint=map will collect the segment wise field values (for the requested size) and merge at shard level and return the shard\_size field values (size \* 1.5 + 10) to the co-ordination node. i.e. Assume the request\_size is 10 and the shard has 8 segments then 8 x 10 unique values will be in on-heap and return 25 field values to co-ordination node.
To be more concise, what is the internal work flow of execution\_mode=map.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 17, 2021, 2:42pm UTC](https://discuss.elastic.co/t/global-ordinals-execution-hint/289699/2 "2021-12-17T14:42:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.