documentation of preserve existing settings
This commit is contained in:
parent
e875f7f72e
commit
59dd4d288a
|
@ -4,8 +4,8 @@
|
||||||
Change specific index level settings in real time.
|
Change specific index level settings in real time.
|
||||||
|
|
||||||
The REST endpoint is `/_settings` (to update all indices) or
|
The REST endpoint is `/_settings` (to update all indices) or
|
||||||
`{index}/_settings` to update one (or more) indices settings. The body
|
`{index}/_settings` to update one (or more) indices settings.
|
||||||
of the request includes the updated settings, for example:
|
The body of the request includes the updated settings, for example:
|
||||||
|
|
||||||
[source,js]
|
[source,js]
|
||||||
--------------------------------------------------
|
--------------------------------------------------
|
||||||
|
@ -21,6 +21,8 @@ PUT /twitter/_settings
|
||||||
|
|
||||||
The list of per-index settings which can be updated dynamically on live
|
The list of per-index settings which can be updated dynamically on live
|
||||||
indices can be found in <<index-modules>>.
|
indices can be found in <<index-modules>>.
|
||||||
|
To preserve existing settings from being updated, the `preserve_existing`
|
||||||
|
request parameter can be set to `true`.
|
||||||
|
|
||||||
[float]
|
[float]
|
||||||
[[bulk]]
|
[[bulk]]
|
||||||
|
|
Loading…
Reference in New Issue