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
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:
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 email@example.com.
To view this discussion on the web visit 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.