# Term stat facet with sort and limit does not return correct result always!

**URL:** <https://discuss.elastic.co/t/term-stat-facet-with-sort-and-limit-does-not-return-correct-result-always/8468>\
**Category:** Elasticsearch\
**Created:** [July 19, 2012, 6:03pm UTC](https://discuss.elastic.co/t/term-stat-facet-with-sort-and-limit-does-not-return-correct-result-always/8468 "2012-07-19T18:03:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gautam\_S](https://avatars.discourse-cdn.com/v4/letter/g/ebca7d/32.png) [@Gautam\_S](https://discuss.elastic.co/u/Gautam_S)\
**Post date:** [July 19, 2012, 6:03pm UTC](https://discuss.elastic.co/t/term-stat-facet-with-sort-and-limit-does-not-return-correct-result-always/8468/1 "2012-07-19T18:03:29Z")

</div>

Hi,  
Have observed that TermStats facet with sort and limit does not return  
correct result always!  
Digging deeper found that the limit is applied after doing sort at each  
shard.  
Is there any specific reason to apply limit at shard level rather than  
doing it at final reducer?  
This behavior is evident when data is a bit sparsed.

However when sort is applied with no limit i.e. (size = 0) it behaves well  
as the sorting happens at the final reducer after merge of data from each  
shard.

Thanks  
Gautam

---

<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, 3:19am UTC](https://discuss.elastic.co/t/term-stat-facet-with-sort-and-limit-does-not-return-correct-result-always/8468/2 "2017-07-06T03:19:47Z")

</div>

Closed on July 6, 2017, 3:19am UTC