[DOCS] Note that DS timestamp field mapping changes require reindex (#58444) (#58517)

With #58096, data streams now track the timestamp field mapping outside
of the template associated with the stream. This means you can no longer
update the timestamp field mapping using template changes.

This updates the associated data stream docs.
This commit is contained in:
James Rodewig 2020-06-24 17:21:26 -04:00 committed by GitHub
parent 1f2e05c947
commit c3f4034199
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 1 deletions

View File

@ -133,6 +133,11 @@ POST /logs/_rollover/
----
// TEST[continued]
====
+
IMPORTANT: You cannot use these methods to change the mapping of a data stream's
<<create-a-data-stream-template,timestamp field>>. To change the timestamp
field's mapping, you must reindex the data stream. See
<<data-streams-use-reindex-to-change-mappings-settings>>.
* To apply mapping and setting changes to all existing backing indices and
future ones, you must create a new data stream and reindex your data into it.

View File

@ -138,7 +138,13 @@ this pattern.
stream.
* A <<date,`date`>> or <<date_nanos,`date_nanos`>> field mapping for the
timestamp field specified in the `timestamp_field` property.
timestamp field specified in the `timestamp_field` property.
+
IMPORTANT: Carefully consider the timestamp field's mapping, including
<<mapping-params,mapping parameters>> such as <<mapping-date-format,`format`>>.
Once the stream is created, you can only update the timestamp field's mapping by
reindexing the data stream. See
<<data-streams-use-reindex-to-change-mappings-settings>>.
* If you intend to use {ilm-init}, you must specify the
<<configure-a-data-stream-ilm-policy,lifecycle policy>> in the