Enabled cannot be updated (#43701)
Removed the invalid tip that enabled can be updated for existing fields and clarified instead that it cannot. Related to #33566 and #33933
This commit is contained in:
parent
86c853a7c2
commit
632da7f2c8
|
@ -89,8 +89,8 @@ GET my_index/_mapping <3>
|
||||||
<2> The document can be retrieved.
|
<2> The document can be retrieved.
|
||||||
<3> Checking the mapping reveals that no fields have been added.
|
<3> Checking the mapping reveals that no fields have been added.
|
||||||
|
|
||||||
TIP: The `enabled` setting can be updated on existing fields
|
The `enabled` setting for existing fields and the top-level mapping
|
||||||
using the <<indices-put-mapping,PUT mapping API>>.
|
definition cannot be updated.
|
||||||
|
|
||||||
Note that because Elasticsearch completely skips parsing the field
|
Note that because Elasticsearch completely skips parsing the field
|
||||||
contents, it is possible to add non-object data to a disabled field:
|
contents, it is possible to add non-object data to a disabled field:
|
||||||
|
|
Loading…
Reference in New Issue