If you add new fields to your mapping, it should work just fine
(they're added to your current mapping). If you try to change the type
of a certain field in your mapping, you will get an error, but
flushing the index doesn't delete your data.
If you need to change the type of a field (let's say from long to
float), you have to reindex your data. You can do that on the live
cluster by scrolling through your data and indexing it in a
different type where you have the new mapping.
Of course if your indices become corrupt for any reason (eg: file
system failure), there's no getting away from backups. But that should
be the same for any database.
http://sematext.com/ -- ElasticSearch -- Solr -- Lucene
On Wed, Oct 17, 2012 at 6:19 PM, Amy firstname.lastname@example.org wrote:
I'm considering using elasticsearch as my primary db, the alternative being
a couchbase-elasticsearch combo.
Group discussions appear positive, but I have an issue that I have not seen
discussed. If I want to change an index mapping, I need to flush the index.
This deletes everything I have stored on Elasticsearch.
Is there an alternative?