# For exporting data shoud we use scroll or pit with search after?

**URL:** <https://discuss.elastic.co/t/for-exporting-data-shoud-we-use-scroll-or-pit-with-search-after/314475>\
**Category:** Elasticsearch\
**Created:** [September 15, 2022, 5:05am UTC](https://discuss.elastic.co/t/for-exporting-data-shoud-we-use-scroll-or-pit-with-search-after/314475 "2022-09-15T05:05:45Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Divit\_Sharma](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/divit_sharma/32/32348_2.png) [@Divit\_Sharma](https://discuss.elastic.co/u/Divit_Sharma)\
**Post date:** [September 21, 2022, 7:13am UTC](https://discuss.elastic.co/t/for-exporting-data-shoud-we-use-scroll-or-pit-with-search-after/314475/5 "2022-09-21T07:13:32Z")

</div>

Thank you @dadoonet

I also had another query about `_scroll`

> [@Sliced scroll returning more hits than normal search (without slice)](https://discuss.elastic.co/t/sliced-scroll-returning-more-hits-than-normal-search-without-slice/314599):
>
> In short, normal search hits \< scroll slice 1 hits + scroll slice 2 hits When I add up sliced scroll hits, it is more than total no of documents returned from single search. Normal search query GET index\*/\_search { "track\_total\_hits": true, "sort": [{ "@timestamp": { "order": "asc", "unmapped\_type": "boolean" } }], "\_source": false, "query": { "bool": { "must": [], "filter": [ { "range": { "@timesta…

---

_[View the full topic](https://discuss.elastic.co/t/for-exporting-data-shoud-we-use-scroll-or-pit-with-search-after/314475)._