2c241e8a36
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. |
||
---|---|---|
.. | ||
community | ||
groovy-api | ||
java-api | ||
perl | ||
python | ||
reference | ||
resiliency | ||
river | ||
ruby | ||
README.asciidoc |
README.asciidoc
The Elasticsearch docs are in AsciiDoc format and can be built using the Elasticsearch documentation build process See: https://github.com/elastic/docs