# Re-index from \_source

**URL:** <https://discuss.elastic.co/t/re-index-from--source/4498>\
**Category:** Elasticsearch\
**Created:** [May 30, 2011, 1:03am UTC](https://discuss.elastic.co/t/re-index-from--source/4498 "2011-05-30T01:03:37Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karma](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@Karma](https://discuss.elastic.co/u/Karma)\
**Post date:** [May 30, 2011, 1:03am UTC](https://discuss.elastic.co/t/re-index-from--source/4498/1 "2011-05-30T01:03:37Z")

</div>

i'm interested in using ES as primary store and looking to ditch  
mongodb, my question regardless roadmap and stabilty towards 1.0, when  
something bad happens, would i be able to re-index by using data from  
ES \_source ?

---

<div class="post-metadata">

**Author:** ![Karma](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@Karma](https://discuss.elastic.co/u/Karma)\
**Post date:** [May 30, 2011, 2:18am UTC](https://discuss.elastic.co/t/re-index-from--source/4498/2 "2011-05-30T02:18:13Z")

</div>

1 more question, how to get response like Auto-Id value from Memcached  
Set?

On May 30, 9:03 am, Karma [akmal...@gmail.com](mailto:akmal...@gmail.com) wrote:

> i'm interested in using ES as primary store and looking to ditch  
> mongodb, my question regardless roadmap and stabilty towards 1.0, when  
> something bad happens, would i be able to re-index by using data from  
> ES \_source ?

---

<div class="post-metadata">

**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\
**Post date:** [May 30, 2011, 1:20pm UTC](https://discuss.elastic.co/t/re-index-from--source/4498/3 "2011-05-30T13:20:53Z")

</div>

re-indexing via source and scan 'search' works nicely.

Be carefully when ditching mongodb as you won't get the document  
immediately after indexing (real time latency of every search  
solution).  
Of course you can work around this via calling expensive refresh (not  
recommended!) or via using the real time version information: set the  
version and when indexing fails due to a version conflict:

1. search to get the latest doc
2. try to index again (until success)

On May 30, 3:03 am, Karma [akmal...@gmail.com](mailto:akmal...@gmail.com) wrote:

> i'm interested in using ES as primary store and looking to ditch  
> mongodb, my question regardless roadmap and stabilty towards 1.0, when  
> something bad happens, would i be able to re-index by using data from  
> ES \_source ?

---

<div class="post-metadata">

**Author:** ![Karma](https://avatars.discourse-cdn.com/v4/letter/k/bcef8e/32.png) [@Karma](https://discuss.elastic.co/u/Karma)\
**Post date:** [May 30, 2011, 2:50pm UTC](https://discuss.elastic.co/t/re-index-from--source/4498/4 "2011-05-30T14:50:02Z")

</div>

Thanks, after hours of creating and playing with golang DB interface  
for ES as data store i came to conclusion, ES was never meant to  
replace a real DB. so i'm back to ES+Mongodb (with \_source disabled)

On May 30, 9:20 pm, Karussell [tableyourt...@googlemail.com](mailto:tableyourt...@googlemail.com) wrote:

> re-indexing via source and scan 'search' works nicely.
> 
> Be carefully when ditching mongodb as you won't get the document  
> immediately after indexing (real time latency of every search  
> solution).  
> Of course you can work around this via calling expensive refresh (not  
> recommended!) or via using the real time version information: set the  
> version and when indexing fails due to a version conflict:
> 
> 1. search to get the latest doc
> 2. try to index again (until success)
> 
> On May 30, 3:03 am, Karma [akmal...@gmail.com](mailto:akmal...@gmail.com) wrote:
> 
> > i'm interested in using ES as primary store and looking to ditch  
> > mongodb, my question regardless roadmap and stabilty towards 1.0, when  
> > something bad happens, would i be able to re-index by using data from  
> > ES \_source ?

---

<div class="post-metadata">

**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\
**Post date:** [May 31, 2011, 11:34am UTC](https://discuss.elastic.co/t/re-index-from--source/4498/5 "2011-05-31T11:34:08Z")

</div>

On May 30, 4:50 pm, Karma [akmal...@gmail.com](mailto:akmal...@gmail.com) wrote:

> Thanks, after hours of creating and playing with golang DB interface  
> for ES as data store i came to conclusion, ES was never meant to  
> replace a real DB.

That's indeed the case, but I'm using it as DB. So what were your  
problems?

---

<div class="post-metadata">

**Author:** ![fashionalwallet](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@fashionalwallet](https://discuss.elastic.co/u/fashionalwallet)\
**Post date:** [June 10, 2011, 3:42am UTC](https://discuss.elastic.co/t/re-index-from--source/4498/6 "2011-06-10T03:42:44Z")

</div>

- deleted -

---

<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, 4:04am UTC](https://discuss.elastic.co/t/re-index-from--source/4498/7 "2017-07-06T04:04:04Z")

</div>


