mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-30 02:13:33 -04:00
Mappings conflicts should not be ignored. If I read the history correctly, this option was added when a mapping update to an existing field was considered a conflict, even if the new mapping was exactly the same. Now that mapping updates are smart enough to detect conflicting options, we don't need an option to ignore conflicts. |
||
---|---|---|
.. | ||
index.asciidoc | ||
migrate_1_0.asciidoc | ||
migrate_1_4.asciidoc | ||
migrate_1_6.asciidoc | ||
migrate_2_0.asciidoc |