# Retrieving sorted results using a point-in-time search with slicing **URL:** \ **Category:** Elasticsearch\ **Created:** [October 18, 2023, 8:58pm UTC](https://discuss.elastic.co/t/retrieving-sorted-results-using-a-point-in-time-search-with-slicing/345328 "2023-10-18T20:58:16Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![valasatava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/valasatava/32/126675_2.png) [@valasatava](https://discuss.elastic.co/u/valasatava)\ **Post date:** [October 18, 2023, 8:58pm UTC](https://discuss.elastic.co/t/retrieving-sorted-results-using-a-point-in-time-search-with-slicing/345328/1 "2023-10-18T20:58:16Z")
Hi everyone, I'm running into issues with retrieving results using [Paginate search results | Elasticsearch Guide [8.10] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/8.10/paginate-search-results.html#slice-scroll) and preserving the sorted order across the whole data set. I need to pull lots of document IDs back and I need them to be sorted. With slice-scroll, the whole set is divided into multiple slices and results are coming back sorted within each slice, but when they are put together in a single list, it look like this: ...,ZZO,ZZQ,ZZR,002,004,006,... - this shows where one slice ends and another starts. I'm using a point-in-time search with slicing. Does someone know if this is an expected behavior for the point-in-time search with slicing? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 15, 2023, 8:59pm UTC](https://discuss.elastic.co/t/retrieving-sorted-results-using-a-point-in-time-search-with-slicing/345328/2 "2023-11-15T20:59:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.