Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[7.17] Clarify update operations may be performed on a data stream's backing indices (#105408) #105413

Merged
merged 1 commit into from
Feb 12, 2024

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Feb 12, 2024

Backports the following commits to 7.17:

@dakrone dakrone added :Data Management/Data streams Data streams and their lifecycles >docs General docs changes auto-merge Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Data Management Meta label for data/management team Team:Docs Meta label for docs team labels Feb 12, 2024
… indices (elastic#105408)

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 d95d6ad)
@elasticsearchmachine elasticsearchmachine merged commit 3318445 into elastic:7.17 Feb 12, 2024
5 checks passed
@dakrone dakrone deleted the backport/7.17/pr-105408 branch February 12, 2024 18:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport :Data Management/Data streams Data streams and their lifecycles >docs General docs changes Team:Data Management Meta label for data/management team Team:Docs Meta label for docs team v7.17.19
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants