-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
Clarify data stream recommendations and best practices #107233
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
dakrone
added
>docs
General docs changes
:Data Management/Data streams
Data streams and their lifecycles
v8.9.3
v8.10.5
v8.11.5
v8.13.1
v8.14.0
v8.12.3
labels
Apr 8, 2024
Documentation preview: |
elasticsearchmachine
added
Team:Data Management
Meta label for data/management team
Team:Docs
Meta label for docs team
labels
Apr 8, 2024
Pinging @elastic/es-docs (Team:Docs) |
Pinging @elastic/es-data-management (Team:Data Management) |
nielsbauman
approved these changes
Apr 8, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, 1 minor comment but overall I think this should remove even more doubts people might have.
dakrone
added
the
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
label
Apr 8, 2024
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2024
* Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
This was referenced Apr 8, 2024
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2024
* Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2024
* Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2024
* Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
dakrone
added a commit
to dakrone/elasticsearch
that referenced
this pull request
Apr 8, 2024
* Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2024
…7238) * Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2024
…7237) * Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2024
…7236) * Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2024
#107234) * Clarify data stream recommendations and best practices (#107233) * Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins. * Remove dlm link
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 8, 2024
… (#107235) * Clarify data stream recommendations and best practices (#107233) * Clarify data stream recommendations and best practices Our documentation around data streams versus aliases could be interpreted in a way where someone doing *any* updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins. * Remove dlm link
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
: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
v8.9.3
v8.10.5
v8.11.5
v8.12.3
v8.13.1
v8.14.0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our documentation around data streams versus aliases could be interpreted in a way where someone doing any updates thinks they need to use an alias with indices instead of a data stream. This commit enhances the documentation around these areas to determine the correct abstraction in a more concrete way. It also tries to clarify that data streams still allow updates to the backing indices, and that a difference is last-write-wins versus first-write-wins.