# Index creation and deployment strategies

**URL:** <https://discuss.elastic.co/t/index-creation-and-deployment-strategies/103580>\
**Category:** Elasticsearch\
**Created:** [October 11, 2017, 4:19pm UTC](https://discuss.elastic.co/t/index-creation-and-deployment-strategies/103580 "2017-10-11T16:19:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gringogordo](https://avatars.discourse-cdn.com/v4/letter/g/a87d85/32.png) [@gringogordo](https://discuss.elastic.co/u/gringogordo)\
**Post date:** [October 11, 2017, 4:19pm UTC](https://discuss.elastic.co/t/index-creation-and-deployment-strategies/103580/1 "2017-10-11T16:19:25Z")

</div>

I have inherited a nice little java app which uses an elasticSearch Index as a back end data source.

At the moment the index is built from scratch every week on a build server and then the service is stopped (on UAT then Live) and the old cluster replaced by the new one.

I am rewriting the app the recreate the index and for various reasons we need to keep doing a full rebuild to replace the existing one each week but I'm thinking there must be a better way than this fairly manual approach ?

Is there a standard approach for this kind of deployment or do people normally live in a world where they are updating / deleting / adding on existing indexes ?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [October 11, 2017, 5:32pm UTC](https://discuss.elastic.co/t/index-creation-and-deployment-strategies/103580/2 "2017-10-11T17:32:23Z")

</div>

You should look at aliases. [https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-aliases.html)  
I think this could help a lot to do that without any interruption.

---

<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:** [November 8, 2017, 5:33pm UTC](https://discuss.elastic.co/t/index-creation-and-deployment-strategies/103580/3 "2017-11-08T17:33:12Z")

</div>

Closed on November 8, 2017, 5:33pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.