# Is ES capable of doing pagination? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 6, 2011, 9:09am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526 "2011-10-06T09:09:41Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![Boris\_Yen](https://avatars.discourse-cdn.com/v4/letter/b/e99b99/32.png) [@Boris\_Yen](https://discuss.elastic.co/u/Boris_Yen)\ **Post date:** [October 6, 2011, 9:09am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/1 "2011-10-06T09:09:41Z")
Hi, I am fairly new to ES. I was wondering if ES is capable of doing the pagination? My use case is if the query result is huge, can ES return a specific amount of data as request? For example, I might only need records 100-200 from the overall result. Regards Boris ---
**Author:** ![Benjamin\_Deveze](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamin_deveze/32/1577_2.png) [@Benjamin\_Deveze](https://discuss.elastic.co/u/Benjamin_Deveze)\ **Post date:** [October 6, 2011, 9:14am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/2 "2011-10-06T09:14:11Z")
You should look at this [http://www.elasticsearch.org/guide/reference/api/search/request-body.html](http://www.elasticsearch.org/guide/reference/api/search/request-body.html) and more precisely the from and size parameters. ---
**Author:** ![Boris\_Yen](https://avatars.discourse-cdn.com/v4/letter/b/e99b99/32.png) [@Boris\_Yen](https://discuss.elastic.co/u/Boris_Yen)\ **Post date:** [October 6, 2011, 9:19am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/3 "2011-10-06T09:19:48Z")
Thanks for the information, it is very useful. One more question, does the data returned from ES contain the total result count when the request contains the size parameters? Thanks in advance Boris On Thu, Oct 6, 2011 at 5:14 PM, Benjamin Devèze [benjamin.deveze@gmail.com](mailto:benjamin.deveze@gmail.com)wrote: > You should look at this > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/search/request-body.html) and > more precisely the from and size parameters. ---
**Author:** ![Benjamin\_Deveze](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benjamin_deveze/32/1577_2.png) [@Benjamin\_Deveze](https://discuss.elastic.co/u/Benjamin_Deveze)\ **Post date:** [October 6, 2011, 9:34am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/4 "2011-10-06T09:34:46Z")
Yeah you will be happy it does contain the total result count. ---
**Author:** ![Jamshid](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jamshid](https://discuss.elastic.co/u/Jamshid)\ **Post date:** [October 7, 2011, 5:19am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/5 "2011-10-07T05:19:07Z")
One thing to keep in mind is that if you are continuously indexing, don't expect to be able to page through the results without missing some items or seeing duplicates. You can use the "scan" search type ([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) reference/api/search/search-type.html) instead if you want a consistent result set that you can page through, but unfortunately you will not be able to sort the results when using "scan". --Jamshid On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > Yeah you will be happy it does contain the total result count. ---
**Author:** ![Boris\_Yen](https://avatars.discourse-cdn.com/v4/letter/b/e99b99/32.png) [@Boris\_Yen](https://discuss.elastic.co/u/Boris_Yen)\ **Post date:** [October 7, 2011, 7:29am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/6 "2011-10-07T07:29:37Z")
Thanks for the information, I will look into it. On Fri, Oct 7, 2011 at 1:19 PM, Jamshid [jamshid69@gmail.com](mailto:jamshid69@gmail.com) wrote: > One thing to keep in mind is that if you are continuously indexing, > don't expect to be able to page through the results without missing > some items or seeing duplicates. > > You can use the "scan" search type ([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > reference/api/search/search-type.html) instead if you want a > consistent result set that you can page through, but unfortunately you > will not be able to sort the results when using "scan". > > --Jamshid > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\ **Post date:** [October 12, 2011, 3:04pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/7 "2011-10-12T15:04:48Z")
scan search type is limited: **Note** scan search type does not support sorting (either on score or a field) or faceting. You can just use a timestamp for every document and filter newer documents away when doing pagination. (same procedure like twitter handles it) On 7 Okt., 07:19, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > One thing to keep in mind is that if you are continuously indexing, > don't expect to be able to page through the results without missing > some items or seeing duplicates. > > You can use the "scan" search type ([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > reference/api/search/search-type.html) instead if you want a > consistent result set that you can page through, but unfortunately you > will not be able to sort the results when using "scan". > > --Jamshid > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![Jamshid](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jamshid](https://discuss.elastic.co/u/Jamshid)\ **Post date:** [October 13, 2011, 7:07pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/8 "2011-10-13T19:07:39Z")
Interesting, I hadn't thought of that. So the timestamp would be the "create date" of the document? Not sure how filtering would work when updating or deleting documents, would elasticsearch keep the updated record in the same "place" while paginating? But I don't see a solution if documents are deleted while paging. --Jamshid On Oct 12, 10:04 am, Karussell [tableyourt...@googlemail.com](mailto:tableyourt...@googlemail.com) wrote: > scan search type is limited: > > **Note** scan search type does not support sorting (either on score or > a field) or faceting. > > You can just use a timestamp for every document and filter newer > documents away when doing pagination. (same procedure like twitter > handles it) > > On 7 Okt., 07:19, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > One thing to keep in mind is that if you are continuously indexing, > > don't expect to be able to page through the results without missing > > some items or seeing duplicates. > > > You can use the "scan" search type ([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > > reference/api/search/search-type.html) instead if you want a > > consistent result set that you can page through, but unfortunately you > > will not be able to sort the results when using "scan". > > > --Jamshid > > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 14, 2011, 12:23pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/9 "2011-10-14T12:23:18Z")
Scan search type is a point in time search, when its executed. You won't see changes (either deletions or new docs) after its first execution. On Thu, Oct 13, 2011 at 9:07 PM, Jamshid [jamshid69@gmail.com](mailto:jamshid69@gmail.com) wrote: > Interesting, I hadn't thought of that. So the timestamp would be the > "create date" of the document? Not sure how filtering would work when > updating or deleting documents, would elasticsearch keep the updated > record in the same "place" while paginating? But I don't see a > solution if documents are deleted while paging. > --Jamshid > > On Oct 12, 10:04 am, Karussell [tableyourt...@googlemail.com](mailto:tableyourt...@googlemail.com) wrote: > > > scan search type is limited: > > > > **Note** scan search type does not support sorting (either on score or > > a field) or faceting. > > > > You can just use a timestamp for every document and filter newer > > documents away when doing pagination. (same procedure like twitter > > handles it) > > > > On 7 Okt., 07:19, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > One thing to keep in mind is that if you are continuously indexing, > > > don't expect to be able to page through the results without missing > > > some items or seeing duplicates. > > > > > You can use the "scan" search type ( > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > > > reference/api/search/search-type.html) instead if you want a > > > consistent result set that you can page through, but unfortunately you > > > will not be able to sort the results when using "scan". > > > > > --Jamshid > > > > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > > > > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![Jamshid](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jamshid](https://discuss.elastic.co/u/Jamshid)\ **Post date:** [October 14, 2011, 6:42pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/10 "2011-10-14T18:42:24Z")
Right, I was referring to Karussell's suggestion of using a timestamp to allow regular (non-"scan") searches to return a consistent set of results. I want sorted results (rules out "scan") and I want to be able to page through the results without missing documents or seeing duplicates. Any suggestions, has this kind of request come up before? Thanks, Jamshid On Oct 14, 7:23 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > Scan search type is a point in time search, when its executed. You won't see > changes (either deletions or new docs) after its first execution. > > On Thu, Oct 13, 2011 at 9:07 PM, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > Interesting, I hadn't thought of that. So the timestamp would be the > > "create date" of the document? Not sure how filtering would work when > > updating or deleting documents, would elasticsearch keep the updated > > record in the same "place" while paginating? But I don't see a > > solution if documents are deleted while paging. > > --Jamshid > > > On Oct 12, 10:04 am, Karussell [tableyourt...@googlemail.com](mailto:tableyourt...@googlemail.com) wrote: > > > > > scan search type is limited: > > > > **Note** scan search type does not support sorting (either on score or > > > a field) or faceting. > > > > You can just use a timestamp for every document and filter newer > > > documents away when doing pagination. (same procedure like twitter > > > handles it) > > > > On 7 Okt., 07:19, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > One thing to keep in mind is that if you are continuously indexing, > > > > don't expect to be able to page through the results without missing > > > > some items or seeing duplicates. > > > > > You can use the "scan" search type ( > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > > > > reference/api/search/search-type.html) instead if you want a > > > > consistent result set that you can page through, but unfortunately you > > > > will not be able to sort the results when using "scan". > > > > > --Jamshid > > > > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) wrote: > > > > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 14, 2011, 6:48pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/11 "2011-10-14T18:48:56Z")
You can use scrolling with search\_type (like the default, query\_then\_fetch), which will guarantee you won't see duplicates or changed data, but, it gets more and more expensive as you scroll through the results. On Fri, Oct 14, 2011 at 8:42 PM, Jamshid [jamshid69@gmail.com](mailto:jamshid69@gmail.com) wrote: > Right, I was referring to Karussell's suggestion of using a timestamp > to allow regular (non-"scan") searches to return a consistent set of > results. > > I want sorted results (rules out "scan") and I want to be able to page > through the results without missing documents or seeing duplicates. > > Any suggestions, has this kind of request come up before? > > Thanks, > Jamshid > > On Oct 14, 7:23 am, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote: > > > Scan search type is a point in time search, when its executed. You won't > > see > > changes (either deletions or new docs) after its first execution. > > > > On Thu, Oct 13, 2011 at 9:07 PM, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > Interesting, I hadn't thought of that. So the timestamp would be the > > > "create date" of the document? Not sure how filtering would work when > > > updating or deleting documents, would elasticsearch keep the updated > > > record in the same "place" while paginating? But I don't see a > > > solution if documents are deleted while paging. > > > --Jamshid > > > > > On Oct 12, 10:04 am, Karussell [tableyourt...@googlemail.com](mailto:tableyourt...@googlemail.com) wrote: > > > > > > > scan search type is limited: > > > > > > **Note** scan search type does not support sorting (either on score > > > > or > > > > a field) or faceting. > > > > > > You can just use a timestamp for every document and filter newer > > > > documents away when doing pagination. (same procedure like twitter > > > > handles it) > > > > > > On 7 Okt., 07:19, Jamshid [jamshi...@gmail.com](mailto:jamshi...@gmail.com) wrote: > > > > > > > One thing to keep in mind is that if you are continuously indexing, > > > > > don't expect to be able to page through the results without missing > > > > > some items or seeing duplicates. > > > > > > > You can use the "scan" search type ( > > > > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/) > > > > > reference/api/search/search-type.html) instead if you want a > > > > > consistent result set that you can page through, but unfortunately > > > > > you > > > > > will not be able to sort the results when using "scan". > > > > > > > --Jamshid > > > > > > > On Oct 6, 9:34 am, Benjamin Devèze [benjamin.dev...@gmail.com](mailto:benjamin.dev...@gmail.com) > > > > > wrote: > > > > > > > > Yeah you will be happy it does contain the total result count. ---
**Author:** ![rodders7884](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@rodders7884](https://discuss.elastic.co/u/rodders7884)\ **Post date:** [October 22, 2013, 3:35pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/12 "2013-10-22T15:35:31Z")
So you can use elastic search queries to page through a large dataset using an offset and limit. If I have 10 million objects to page through, and want them 1000 at a time (say) will the search be very slow when I ask for "The next 1000 items starting with the 9 millionth item" ? ---
**Author:** ![Oli\_McCormack](https://avatars.discourse-cdn.com/v4/letter/o/fbc32d/32.png) [@Oli\_McCormack](https://discuss.elastic.co/u/Oli_McCormack)\ **Post date:** [October 23, 2013, 8:11pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/13 "2013-10-23T20:11:18Z")
Yes, it will get slower the farther through the result set you get. It needs to perform a query for results as far as the (offset+limit) doc, then select/return the 1000 docs you wanted in the page. The proposed alternative which does not incur this same performance hit is to use a scan/scroll query, which keeps a result set open for a period of time as you page over it. See the section on scan here[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-search-type.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-search-type.html) . On Tue, Oct 22, 2013 at 8:35 AM, rodders7884 [rod.french@gmail.com](mailto:rod.french@gmail.com) wrote: > So you can use Elasticsearch queries to page through a large dataset using > an offset and limit. > > If I have 10 million objects to page through, and want them 1000 at a time > (say) will the search be very slow when I ask for "The next 1000 items > starting with the 9 millionth item" ? > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4042984.html](http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4042984.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![PrasathRajan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prasathrajan/32/52874_2.png) [@PrasathRajan](https://discuss.elastic.co/u/PrasathRajan)\ **Post date:** [July 22, 2014, 1:16pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/14 "2014-07-22T13:16:05Z")
can somebody suggest.. Is it possible to jump over Page Nos [forward/backward]while using Scan/Scroll for Pagination?.. Or any other effective way available for pagination?. ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [July 23, 2014, 1:36pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/15 "2014-07-23T13:36:00Z")
Hi Prasath, Scan and scroll can only move forward. If you want to have previous/next buttons, you would typically run the query once again with different values of `from` and `size`. On Tue, Jul 22, 2014 at 3:16 PM, PrasathRajan [prasanth.sunrise@gmail.com](mailto:prasanth.sunrise@gmail.com) wrote: > can somebody suggest.. > > Is it possible to jump over Page Nos [forward/backward]while using > Scan/Scroll for Pagination?.. Or any other effective way available for > pagination?. > > -- > View this message in context: > [http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4060343.html](http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4060343.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/1406034965952-4060343.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1406034965952-4060343.post%40n3.nabble.com) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- Adrien Grand -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [July 23, 2014, 1:55pm UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/16 "2014-07-23T13:55:30Z")
Scan/scroll is also not for exposing to "web scale" users. Fine for tens of users, not for millions. There is non-trivial cost on the cluster during scan/scroll. For the most part we just use from and size. There is a setting called preference that might be worth looking at if you expect lots of scrolling. Don't allow super deep scrolling - there are some portions of query execution that end up having to do from + size amounts of work (O(n\*log(n) of it). And they need O(from + size) of memory too. So going too deep can take up tons of memory. Nik On Wed, Jul 23, 2014 at 9:36 AM, Adrien Grand \< [adrien.grand@elasticsearch.com](mailto:adrien.grand@elasticsearch.com)\> wrote: > Hi Prasath, > > Scan and scroll can only move forward. If you want to have previous/next > buttons, you would typically run the query once again with different values > of `from` and `size`. > > On Tue, Jul 22, 2014 at 3:16 PM, PrasathRajan [prasanth.sunrise@gmail.com](mailto:prasanth.sunrise@gmail.com) > wrote: > > > can somebody suggest.. > > > > Is it possible to jump over Page Nos [forward/backward]while using > > Scan/Scroll for Pagination?.. Or any other effective way available for > > pagination?. > > > > -- > > View this message in context: > > [http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4060343.html](http://elasticsearch-users.115913.n3.nabble.com/Is-ES-capable-of-doing-pagination-tp3399087p4060343.html) > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/1406034965952-4060343.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1406034965952-4060343.post%40n3.nabble.com) > > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). > > -- > Adrien Grand > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j6y-hQudM4utSi-JJakdMrkJLXN90MwRa8Tu9xpuhnbyA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2ygvWv0%2BuaQ1UNpoJwksu\_sRLPdUw3cz5-gsf-uDEF%3Dw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd2ygvWv0%2BuaQ1UNpoJwksu_sRLPdUw3cz5-gsf-uDEF%3Dw%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 1:13am UTC](https://discuss.elastic.co/t/is-es-capable-of-doing-pagination/5526/17 "2017-07-06T01:13:55Z")