Hi, We've constantly facing with updates/changes in our document mapping during development, so we've come up with a idea of using `doc_type` for versioning. Basically we start from a `doc_type` like: `thing_0` as the start point. And each time we have some changes in the mapping, we created a updated version of mapping and put it under a new `doc_type` like : `thing_1`. Then we switch all our systems to the new doc_type `thing_1`. And asynchronously we migrate the data from old version, `thing_0`, to the new doc_type `thing_1`, or simple delete them.
One thing remains a problem: asynchronously migration means that at some point, we may have multiple doc_types in a single index (maybe 10+). Will this become a problem for ElasticSearch? (performance?) Otherwise, do you guys thinks it's a good idea for versioning document mappings? How do you handle changes in the mapping? Thanks. -- 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 protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2408833a-b9bd-4875-9526-0d61ad215f33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
