honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-17 10:25:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add note to docs on duplicate keys in config

Browse Source 
This commit adds a note to the migration docs that duplicate keys in the
configuration file are no longer permitted.

Relates #24022
This commit is contained in:
Jason Tedor 2017-04-10 10:58:59 -04:00 committed by GitHub
parent 37aadb2adf
commit 669fcd05e6
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/reference/migration/migrate_6_0/settings.asciidoc
View File

@ -1,6 +1,32 @@
[[breaking_60_settings_changes]] [[breaking_60_settings_changes]]
=== 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 ==== Coercion of boolean settings
Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0 Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0