# \#point-in-time **URL:** https://discuss.elastic.co/tag/point-in-time/103.md [Latest](https://discuss.elastic.co/latest.md) · [Categories](https://discuss.elastic.co/categories.md) · [Tags](https://discuss.elastic.co/tags.md) --- ## [Point in time Expiry!](https://discuss.elastic.co/t/point-in-time-expiry/371670)
**Author:** [@Mohammad\_Saif](https://discuss.elastic.co/u/Mohammad_Saif)\ **Replies:** 0\ **Last updated:** [December 9, 2024, 6:07am UTC](https://discuss.elastic.co/t/point-in-time-expiry/371670 "2024-12-09T06:07:14Z")
I created a point in time with expiry set as 15 min, and i have observed that if the query(this query is not extending the pit ,i.e. keep-alive ) using the pit is running close to the expiry, then this pit is not getting… --- ## [Understanding the scope and data coverage of Point in Time (PIT) snapshots in Elasticsearch](https://discuss.elastic.co/t/understanding-the-scope-and-data-coverage-of-point-in-time-pit-snapshots-in-elasticsearch/364148)
**Author:** [@Hamza\_Belmellouki](https://discuss.elastic.co/u/Hamza_Belmellouki)\ **Replies:** 0\ **Last updated:** [July 31, 2024, 4:07pm UTC](https://discuss.elastic.co/t/understanding-the-scope-and-data-coverage-of-point-in-time-pit-snapshots-in-elasticsearch/364148 "2024-07-31T16:07:00Z")
Hello, I'm working with Elasticsearch and utilizing the Point in Time (PIT) feature for my queries. I understand that PIT creates a snapshot(kind of) of the data to ensure consistent results across multiple searches, bu… --- ## [Slicing without point in time](https://discuss.elastic.co/t/slicing-without-point-in-time/341765)
**Author:** [@kmcclellan](https://discuss.elastic.co/u/kmcclellan)\ **Replies:** 0\ **Last updated:** [August 27, 2023, 10:04pm UTC](https://discuss.elastic.co/t/slicing-without-point-in-time/341765 "2023-08-27T22:04:13Z")
When you specify "slices" for a search request, you will receive an error if the search is not a point-in-time or scrolled query: "\[slice\] can only be used with \[scroll\] or \[point-in-time\] requests". I don't quite under… --- ## [Collapse not working with search\_after with single sort field and PIT](https://discuss.elastic.co/t/collapse-not-working-with-search-after-with-single-sort-field-and-pit/316165)
**Author:** [@Reese\_Allison](https://discuss.elastic.co/u/Reese_Allison)\ **Replies:** 1\ **Last updated:** [October 11, 2022, 3:30pm UTC](https://discuss.elastic.co/t/collapse-not-working-with-search-after-with-single-sort-field-and-pit/316165 "2022-10-11T15:30:06Z")
I have an Elastic query that initially returns results. When I attempt the query again using search\_after for paging, I am getting the error: Cannot use \[collapse\] in conjunction with \[search\_after\] unless the search is … --- ## [Point In Time for multi threaded queries / slices](https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243)
**Author:** [@str8y](https://discuss.elastic.co/u/str8y)\ **Replies:** 0\ **Last updated:** [October 10, 2022, 3:51pm UTC](https://discuss.elastic.co/t/point-in-time-for-multi-threaded-queries-slices/316243 "2022-10-10T15:51:19Z")
Hi, I read in the documentation that every result could contain an updated id for the pit I created, which I have to use in subsequent search requests. How does that behave in scenarios where I'm using multiple searche… --- ## [PIT on alias with filter](https://discuss.elastic.co/t/pit-on-alias-with-filter/306715)
**Author:** [@mhugo](https://discuss.elastic.co/u/mhugo)\ **Replies:** 0\ **Last updated:** [June 8, 2022, 2:42pm UTC](https://discuss.elastic.co/t/pit-on-alias-with-filter/306715 "2022-06-08T14:42:28Z")
Hi, I am trying to understand the resource demand for pagination queries over large datasets using search\_after and a Point-In-Time. The application I work on exposes "datasets" to its customers. These datasets may be … --- ## [Collapse with point in time feature](https://discuss.elastic.co/t/collapse-with-point-in-time-feature/301535)
**Author:** [@nabhan\_karmi](https://discuss.elastic.co/u/nabhan_karmi)\ **Replies:** 1\ **Last updated:** [April 7, 2022, 7:35am UTC](https://discuss.elastic.co/t/collapse-with-point-in-time-feature/301535 "2022-04-07T07:35:17Z")
I'm trying to use the collapse feature with the point in time, I successfully make the two features run together as per documentation, but the problem is with the result, in my case I have 3 documents has the same value … --- ## [TimeValue error on XContentBuilder](https://discuss.elastic.co/t/timevalue-error-on-xcontentbuilder/299012)
**Author:** [@dancerjohn](https://discuss.elastic.co/u/dancerjohn)\ **Replies:** 7\ **Last updated:** [March 11, 2022, 2:14pm UTC](https://discuss.elastic.co/t/timevalue-error-on-xcontentbuilder/299012 "2022-03-11T14:14:47Z")
Getting IllegalArgumentException ("cannot write xcontent for unknown value of type TimeValue") even though org.Elasticsearch.common.unit.TimeValue is an elastic class and is used in org.Elasticsearch.search.builder.Point… --- ## [Point In Time creation failure after upgrade](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172)
**Author:** [@RapTvin](https://discuss.elastic.co/u/RapTvin)\ **Replies:** 2\ **Last updated:** [January 25, 2022, 12:50pm UTC](https://discuss.elastic.co/t/point-in-time-creation-failure-after-upgrade/295172 "2022-01-25T12:50:38Z")
Hello, I need some help in an issue, I recently upgraded my Elasticsearch on local setup ( i.e downloaded 7.16.2 ). Now when I try to run a Point in Time API to retrieve the PIT id, on the Elasticsearch logs it gives me … --- ## [Should I close the older PIT id once it has been replaced by a new PIT id?](https://discuss.elastic.co/t/should-i-close-the-older-pit-id-once-it-has-been-replaced-by-a-new-pit-id/293420)
**Author:** [@pranay\_jain](https://discuss.elastic.co/u/pranay_jain)\ **Replies:** 0\ **Last updated:** [January 4, 2022, 8:51am UTC](https://discuss.elastic.co/t/should-i-close-the-older-pit-id-once-it-has-been-replaced-by-a-new-pit-id/293420 "2022-01-04T08:51:24Z")
I am working on a task in which I have to search a large number of documents in Elasticsearch. I use SearchAPI with SearchAfter and PointInTime as recommended. While fetching the results, I am using the PIT ID returned b… --- ## [Point In Time Search using wild card index](https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329)
**Author:** [@rohith511](https://discuss.elastic.co/u/rohith511)\ **Replies:** 0\ **Last updated:** [November 27, 2021, 9:36am UTC](https://discuss.elastic.co/t/point-in-time-search-using-wild-card-index/290329 "2021-11-27T09:36:02Z")
Sometime back when we created elastic we created multiple indexes with same initial pattern and these are dynamic suffix. (eg : microservice\_logs\_XYZ , microservice\_logs\_abc , microservice\_logs\_pqr etc..) Not sure the… --- ## [General elastic performance when search\_after with PIT sorted by score is used for UI pagination](https://discuss.elastic.co/t/general-elastic-performance-when-search-after-with-pit-sorted-by-score-is-used-for-ui-pagination/287238)
**Author:** [@vjgorla](https://discuss.elastic.co/u/vjgorla)\ **Replies:** 1\ **Last updated:** [October 26, 2021, 9:17pm UTC](https://discuss.elastic.co/t/general-elastic-performance-when-search-after-with-pit-sorted-by-score-is-used-for-ui-pagination/287238 "2021-10-26T21:17:13Z")
We are integrating search\_after query to our UI pagination. If we use PIT and keep the search context alive between UI page fetches, which could be minutes depending on user think time, would that scale well?. We have to… --- ## [Fetch data from a middle of a big stack using searchAfter( jump to a specific page)](https://discuss.elastic.co/t/fetch-data-from-a-middle-of-a-big-stack-using-searchafter-jump-to-a-specific-page/285256)
**Author:** [@Fat](https://discuss.elastic.co/u/Fat)\ **Replies:** 4\ **Last updated:** [October 1, 2021, 8:18am UTC](https://discuss.elastic.co/t/fetch-data-from-a-middle-of-a-big-stack-using-searchafter-jump-to-a-specific-page/285256 "2021-10-01T08:18:13Z")
Hi All I have a large data set around 25million records I am using searchAfter with PointInTime to walk through the data My question is there a way where I can skip records over the limit of 10000 index.max\_result\_w…