# Real time indexes

**URL:** <https://discuss.elastic.co/t/real-time-indexes/2206>\
**Category:** Elasticsearch\
**Created:** [June 9, 2015, 11:34am UTC](https://discuss.elastic.co/t/real-time-indexes/2206 "2015-06-09T11:34:25Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ton](https://avatars.discourse-cdn.com/v4/letter/t/e0b2c6/32.png) [@ton](https://discuss.elastic.co/u/ton)\
**Post date:** [June 9, 2015, 11:34am UTC](https://discuss.elastic.co/t/real-time-indexes/2206/1 "2015-06-09T11:34:25Z")

</div>

does elasticsearch support real time indexes ?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 9, 2015, 12:52pm UTC](https://discuss.elastic.co/t/real-time-indexes/2206/2 "2015-06-09T12:52:05Z")

</div>

Could you explain what you mean? "Real time" means different things in different contexts and to different people.

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [June 9, 2015, 12:57pm UTC](https://discuss.elastic.co/t/real-time-indexes/2206/3 "2015-06-09T12:57:05Z")

</div>

Updates usually hit the index in around a second if that is what you are looking for.

---

<div class="post-metadata">

**Author:** ![ton](https://avatars.discourse-cdn.com/v4/letter/t/e0b2c6/32.png) [@ton](https://discuss.elastic.co/u/ton)\
**Post date:** [June 9, 2015, 1:26pm UTC](https://discuss.elastic.co/t/real-time-indexes/2206/4 "2015-06-09T13:26:00Z")

</div>

Yes, this is what i was looking for,  
is there a way using the api to index and get back response only after the index updated ?

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [June 9, 2015, 1:45pm UTC](https://discuss.elastic.co/t/real-time-indexes/2206/5 "2015-06-09T13:45:30Z")

</div>

> [@ton](#):
>
> is there a way using the api to index and get back response only after the index updated ?

No but there is a way to force a refresh - which is ok for very low traffic indexes. Here is the discussion around blocking a request until something is visible:

> <https://github.com/elastic/elasticsearch/issues/1063>
>
> Feature request: Provide an option to the index operation that will wait until …the next scheduled refresh occurs before returning a response. After the response is returned, all documents indexed in that operation should be visible for search.

---

<div class="post-metadata">

**Author:** ![ton](https://avatars.discourse-cdn.com/v4/letter/t/e0b2c6/32.png) [@ton](https://discuss.elastic.co/u/ton)\
**Post date:** [June 10, 2015, 6:53am UTC](https://discuss.elastic.co/t/real-time-indexes/2206/6 "2015-06-10T06:53:15Z")

</div>

Thank you ,  
is this apply also for in memory index ?

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [June 10, 2015, 6:56am UTC](https://discuss.elastic.co/t/real-time-indexes/2206/7 "2015-06-10T06:56:00Z")

</div>

I'm not sure what you mean, but _all_ query operations are only current as of the most recent refresh. Changes that have taken place after the refresh are effectively not visible when querying. However, getting a document by id guarantees a consistent result.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:08am UTC](https://discuss.elastic.co/t/real-time-indexes/2206/8 "2017-07-06T00:08:41Z")

</div>