# Reindex or Clone index (version 1.4) **URL:** \ **Category:** Elasticsearch\ **Created:** [June 28, 2019, 4:06pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086 "2019-06-28T16:06:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![cehdmoy](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cehdmoy](https://discuss.elastic.co/u/cehdmoy)\ **Post date:** [June 28, 2019, 4:06pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086/1 "2019-06-28T16:06:22Z")
Hi all, this is my user case My team has built a solution to index from scratch around 30.000 documents into ES. But the whole process is taking around 2 hours. Not because of ES, it's because to retrieve the data needed to recreate all files from scratch takes too long. For this reason, we wanna change the strategy, and not recreate all index. Instead, we want to just update some files (maybe 40% of them, defines for business rules), and take metrics to compare. The new strategy looks like this: We wanna create two indexes, let call them index\_A and index\_B, both cloned from production index. Then for an update by a batch process, update both indexes and choose index\_A to production. Then when running again the batch process it will be executed against index\_B, then we gonna flip the indexes and finally apply same updates to index\_A for consistency. But to start this strategy we need to "clone" the production index. We don't' want to create from scratch indexes over an over again. **Here is my question:** How could we clone or copy or reindex the index, please notice that reindex API isn't defined for V1.4 according to my understanding. Any suggestions or workaround to archive that. Thanks in advance. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 28, 2019, 4:36pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086/2 "2019-06-28T16:36:36Z")
Why are you using version 1.4 if you are developing a new solution?? ---
**Author:** ![cehdmoy](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@cehdmoy](https://discuss.elastic.co/u/cehdmoy)\ **Post date:** [June 28, 2019, 4:41pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086/3 "2019-06-28T16:41:40Z")
That's a good question. It's because the indexing process is just a part of the whole process and services, and there is a lot of legacy code in there that is implemented using this version of ES. So update the version isn't trivial. I would love just update it but doesn't look like an option by now sadly. Regards. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [June 28, 2019, 4:52pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086/4 "2019-06-28T16:52:11Z")
I have “cloned” indices using snapshot and restore before, but do not remember when that was introduced. Version 1.4 is almost 5 years old if I remember correctly so I would warmly recommend upgrading (at least to the last 1.7.x release which should be compatible). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 26, 2019, 4:52pm UTC](https://discuss.elastic.co/t/reindex-or-clone-index-version-1-4/188086/5 "2019-07-26T16:52:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.