# Specifying size in Scroll API

**URL:** <https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109>\
**Category:** Elasticsearch\
**Created:** [May 5, 2020, 9:03am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109 "2020-05-05T09:03:42Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![guruprasadkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guruprasadkk/32/66271_2.png) [@guruprasadkk](https://discuss.elastic.co/u/guruprasadkk)\
**Post date:** [May 5, 2020, 9:03am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/1 "2020-05-05T09:03:43Z")

</div>

I want to use scroll for my pagination. I know that in the initial search request I can specify the "size",  
Is it possible to specify the size in the subsequent scroll requests.  
My use case is like this  
In first batch get 10  
In second batch get 10  
In third batch I want to get only 5

Is there any way to tell scroll API that I want these many records only?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [May 5, 2020, 9:47am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/2 "2020-05-05T09:47:40Z")

</div>

I don't see such an option.  
But you can always get the 10 results back on the 3rd request and in your application just get the 5 first you need.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [May 5, 2020, 10:00am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/3 "2020-05-05T10:00:27Z")

</div>

Why use scroll queries for pagination of small result sets? Each scroll query will keep a context that has a certain lifetime and puts a hold on the underlying segments, potentially preventing merging.

---

<div class="post-metadata">

**Author:** ![guruprasadkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guruprasadkk/32/66271_2.png) [@guruprasadkk](https://discuss.elastic.co/u/guruprasadkk)\
**Post date:** [May 5, 2020, 10:48am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/4 "2020-05-05T10:48:14Z")

</div>

That was just example. Actually we want to get in batches of 50k

---

<div class="post-metadata">

**Author:** ![guruprasadkk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guruprasadkk/32/66271_2.png) [@guruprasadkk](https://discuss.elastic.co/u/guruprasadkk)\
**Post date:** [May 5, 2020, 10:48am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/5 "2020-05-05T10:48:20Z")

</div>

Ok. thanks.

---

<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:** [June 2, 2020, 10:48am UTC](https://discuss.elastic.co/t/specifying-size-in-scroll-api/231109/6 "2020-06-02T10:48:25Z")

</div>

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