# How to work with mapping evolution in production?

**URL:** <https://discuss.elastic.co/t/how-to-work-with-mapping-evolution-in-production/15401>\
**Category:** Elasticsearch\
**Created:** [January 24, 2014, 10:53am UTC](https://discuss.elastic.co/t/how-to-work-with-mapping-evolution-in-production/15401 "2014-01-24T10:53:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Han\_JU](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/han_ju/32/962_2.png) [@Han\_JU](https://discuss.elastic.co/u/Han_JU)\
**Post date:** [January 24, 2014, 10:53am UTC](https://discuss.elastic.co/t/how-to-work-with-mapping-evolution-in-production/15401/1 "2014-01-24T10:53:21Z")

</div>

Hi,

We've already release our public beta and it's backed by a ElasticSearch  
cluster as our main document store, it works like a charm in production.  
Now we are facing a new problem is mapping evolution. For new feature, new  
kinds of query needed by front-end, the mapping need to be modified: add a  
new analyzer, change the way one particular field is analyzed, rename some  
fields etc.  
For us, an obvious solution is to "freeze" the old index and create a new  
index with the new mapping, then re-index the content of the old into the  
new index. But it needs lots of care since it's production data and  
reindexing is time consuming.  
So my question here is do we have a better solution for this problem? How  
you guys work with this in production settings?

We're using 0.90.7.

Many thanks in advance.

BTW, if you need to know more about your website, have a try of our app:

> **[Botify | Website crawler & Log analyzer for SEO](https://www.botify.com/)**
>
> Increase your SEO traffic and revenue with great actionable data

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8582055d-58df-4faf-8291-fdff531b7f36%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8582055d-58df-4faf-8291-fdff531b7f36%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Binh\_Ly](https://avatars.discourse-cdn.com/v4/letter/b/ce7236/32.png) [@Binh\_Ly](https://discuss.elastic.co/u/Binh_Ly)\
**Post date:** [January 24, 2014, 6:00pm UTC](https://discuss.elastic.co/t/how-to-work-with-mapping-evolution-in-production/15401/2 "2014-01-24T18:00:37Z")

</div>

Han:

Maybe this article might help:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

On Friday, January 24, 2014 5:53:21 AM UTC-5, Han JU wrote:

> Hi,
> 
> We've already release our public beta and it's backed by a Elasticsearch  
> cluster as our main document store, it works like a charm in production.  
> Now we are facing a new problem is mapping evolution. For new feature, new  
> kinds of query needed by front-end, the mapping need to be modified: add a  
> new analyzer, change the way one particular field is analyzed, rename some  
> fields etc.  
> For us, an obvious solution is to "freeze" the old index and create a new  
> index with the new mapping, then re-index the content of the old into the  
> new index. But it needs lots of care since it's production data and  
> reindexing is time consuming.  
> So my question here is do we have a better solution for this problem? How  
> you guys work with this in production settings?
> 
> We're using 0.90.7.
> 
> Many thanks in advance.
> 
> BTW, if you need to know more about your website, have a try of our app:  
> [www.botify.com](http://www.botify.com)

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/958b1887-5c98-4851-944a-8b35a5635850%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/958b1887-5c98-4851-944a-8b35a5635850%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 1:54am UTC](https://discuss.elastic.co/t/how-to-work-with-mapping-evolution-in-production/15401/3 "2017-07-06T01:54:55Z")

</div>