# Elastic Search Record Availability Time

**URL:** https://discuss.elastic.co/t/elastic-search-record-availability-time/34883
**Category:** Elasticsearch
**Created:** [November 18, 2015, 6:55am UTC](https://discuss.elastic.co/t/elastic-search-record-availability-time/34883 "2015-11-18T06:55:09Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [November 18, 2015, 8:02am UTC](https://discuss.elastic.co/t/elastic-search-record-availability-time/34883/2 "2015-11-18T08:02:51Z")

</div>

Do you mean available by the document get API? You discovered the near real time feature of a document.

See

> [@Just Pushed: Versioning](https://discuss.elastic.co/t/just-pushed-versioning/3735):
>
> The versioning feature allows to handle conflicts when doing a get/search and then index/delete. Each document has a version number, and each index and delete (tombstone) increase the version number. A conflict is detected when providing a version parameter to the index/delete request and there is a mismatch between the version provided and the real time version of the current document. If a version number is not provided, then the operation is forced without doing any version check. Sear…

and

> **[Elasticsearch Versioning Support](https://www.elastic.co/blog/elasticsearch-versioning-support)**

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-record-availability-time/34883)._