# Elastic aggregation scrolling **URL:** \ **Category:** Elasticsearch\ **Created:** [August 23, 2015, 9:19am UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894 "2015-08-23T09:19:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Giladovich](https://avatars.discourse-cdn.com/v4/letter/g/a183cd/32.png) [@Giladovich](https://discuss.elastic.co/u/Giladovich)\ **Post date:** [August 23, 2015, 9:19am UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894/1 "2015-08-23T09:19:34Z")
Is there an architectural reason elastic doesn't provide aggregation scrolling? Is it just not yet implemented, or is there a profound reason that it is not provided? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 23, 2015, 10:13pm UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894/2 "2015-08-23T22:13:45Z")
Do you mean aggs over a scroll, or an agg you can scroll through? ---
**Author:** ![Giladovich](https://avatars.discourse-cdn.com/v4/letter/g/a183cd/32.png) [@Giladovich](https://discuss.elastic.co/u/Giladovich)\ **Post date:** [August 24, 2015, 7:41am UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894/3 "2015-08-24T07:41:19Z")
Hey, I mean Agg you can scroll through. Let's say my query term-aggregates documents by specific field, but that field has very high cardinality. I would like to scroll and get the aggregated results of different keys on each scroll. Every key aggregation should be complete and consider all relevant documents regardless of the scrolling of keys, of course. ---
**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\ **Post date:** [August 24, 2015, 7:49am UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894/4 "2015-08-24T07:49:42Z")
Putting aside the performance concerns, there is complex user logic. Unlike a tabular query result set with aggs you potentially have many nested sets organised in a complex tree (the top ten Xs for each of the top ten Ys...). When you ask for "the next page" you would potentially need to provide complex context to define which branch, sub-branch and leaf nodes you are asking to be paged in the overall tree. ---
**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:54pm UTC](https://discuss.elastic.co/t/elastic-aggregation-scrolling/27894/5 "2017-07-05T23:54:13Z")