Jason Tedor 32b2caad42 Correct handling of default and array settings ...

In Elasticsearch 5.3.0 a bug was introduced in the merging of default
settings when the target setting existed as an array. This arose due to
the fact that when a target setting is an array, the setting key is
broken into key.0, key.1, ..., key.n, one for each element of the
array. When settings are replaced by default.key, we are looking for the
target key but not the target key.0. This leads to key, and key.0, ...,
key.n being present in the constructed settings object. This commit
addresses two issues here. The first is that we fix the merging of the
keys so that when we try to merge default.key, we also check for the
presence of the flattened keys. The second is that when we try to get a
setting value as an array from a settings object, we check whether or
not the backing map contains the top-level key as well as the flattened
keys. This latter check would have caught the first bug. For kicks, we
add some tests.

Relates #24074

2017-04-13 06:34:58 -04:00

..

licenses

Build: Switch jna dependency to an elastic version (#24081)

2017-04-13 00:17:50 -07:00

src

Correct handling of default and array settings

2017-04-13 06:34:58 -04:00

build.gradle

Build: Switch jna dependency to an elastic version (#24081)

2017-04-13 00:17:50 -07:00