# Clarification needed: Changing PIT IDs in Elasticsearch

**URL:** <https://discuss.elastic.co/t/clarification-needed-changing-pit-ids-in-elasticsearch/364154>\
**Category:** Elasticsearch\
**Created:** [July 31, 2024, 4:41pm UTC](https://discuss.elastic.co/t/clarification-needed-changing-pit-ids-in-elasticsearch/364154 "2024-07-31T16:41:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hamza\_Belmellouki](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hamza_belmellouki/32/136426_2.png) [@Hamza\_Belmellouki](https://discuss.elastic.co/u/Hamza_Belmellouki)\
**Post date:** [July 31, 2024, 4:41pm UTC](https://discuss.elastic.co/t/clarification-needed-changing-pit-ids-in-elasticsearch/364154/1 "2024-07-31T16:41:22Z")

</div>

The Elasticsearch documentation for version 7.17 states:

> The open point in time request and each subsequent search request can return different `id`; thus always use the most recently received `id` for the next search request.

(Source: [Point in time API | Elasticsearch Guide [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/point-in-time-api.html))

This statement is unclear. When the documentation mentions that subsequent requests can return different PIT `id`s, it's not evident whether:

1. A new Point in Time (PIT) context has been created, or
2. The `id` has changed, but we're still operating within the same PIT context.

Clarification on this point would be helpful for understanding the behavior and proper usage of the Point in Time API.

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [August 1, 2024, 9:30am UTC](https://discuss.elastic.co/t/clarification-needed-changing-pit-ids-in-elasticsearch/364154/2 "2024-08-01T09:30:32Z")

</div>

I think the docs are incorrect here, see [Users should rely on PIT ID never changing · Issue #105274 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/issues/105274).
