From 562dc31a8852e03f08776a6d2e1617a5c2513e88 Mon Sep 17 00:00:00 2001 From: Lee Hinman Date: Mon, 12 Feb 2024 12:19:52 -0700 Subject: [PATCH] Clarify update operations may be performed on a data stream's backing indices (#105408) (#105416) These statements come off a little too strongly towards "don't use data streams if you *ever* have updates", but they do support updates when necessary, as long as the backing indices are used. (cherry picked from commit d95d6adae5fd76d2e7cef620cf963cee55d85fb2) --- docs/reference/alias.asciidoc | 5 +++-- docs/reference/ilm/ilm-tutorial.asciidoc | 10 +++++----- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/reference/alias.asciidoc b/docs/reference/alias.asciidoc index 552b2addbbda4..6ddd3602e1467 100644 --- a/docs/reference/alias.asciidoc +++ b/docs/reference/alias.asciidoc @@ -240,8 +240,9 @@ POST _aliases include::{es-repo-dir}/indices/aliases.asciidoc[tag=write-index-defaults] TIP: We recommend using data streams to store append-only time series data. If -you frequently update or delete existing time series data, use an index alias -with a write index instead. See +you need to update or delete existing time series data, you can perform update or delete operations +directly on the data stream backing index. If you frequently send multiple documents using the same +`_id` expecting last-write-wins, you may want to use an index alias with a write index instead. See <>. [discrete] diff --git a/docs/reference/ilm/ilm-tutorial.asciidoc b/docs/reference/ilm/ilm-tutorial.asciidoc index 519eb03b1e7dd..c7f2c3537b5e8 100644 --- a/docs/reference/ilm/ilm-tutorial.asciidoc +++ b/docs/reference/ilm/ilm-tutorial.asciidoc @@ -14,11 +14,11 @@ requirements for your newest data, control costs over time, enforce retention po and still get the most out of your data. TIP: Data streams are best suited for -<> use cases. If you need to frequently -update or delete existing documents across multiple indices, we recommend -using an index alias and index template instead. You can still use ILM to -manage and rollover the alias's indices. Skip to -<>. +<> use cases. If you need to update or delete existing time +series data, you can perform update or delete operations directly on the data stream backing index. +If you frequently send multiple documents using the same `_id` expecting last-write-wins, you may +want to use an index alias with a write index instead. You can still use ILM to manage and rollover +the alias's indices. Skip to <>. To automate rollover and management of a data stream with {ilm-init}, you: