From 669fcd05e6eda64db6eaf8ca31ebaaeaa85dd443 Mon Sep 17 00:00:00 2001 From: Jason Tedor Date: Mon, 10 Apr 2017 10:58:59 -0400 Subject: [PATCH] Add note to docs on duplicate keys in config This commit adds a note to the migration docs that duplicate keys in the configuration file are no longer permitted. Relates #24022 --- .../migration/migrate_6_0/settings.asciidoc | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/reference/migration/migrate_6_0/settings.asciidoc b/docs/reference/migration/migrate_6_0/settings.asciidoc index ec25ffb601c..44acb999394 100644 --- a/docs/reference/migration/migrate_6_0/settings.asciidoc +++ b/docs/reference/migration/migrate_6_0/settings.asciidoc @@ -1,6 +1,32 @@ [[breaking_60_settings_changes]] === Settings changes +==== Duplicate keys in configuration file + +In previous versions of Elasticsearch, the configuration file was allowed to +contain duplicate keys. For example: + +[source,yaml] +-------------------------------------------------- +node: + name: my-node + +node + attr: + rack: my-rack +-------------------------------------------------- + +In Elasticsearch 6.0.0, this is no longer permitted. Instead, this must be +specified in a single key as: + +[source,yaml] +-------------------------------------------------- +node: + name: my-node + attr: + rack: my-rack +-------------------------------------------------- + ==== Coercion of boolean settings Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0