Clarify data stream recommendations and best practices#107233
Merged
dakrone merged 2 commits intoelastic:mainfrom Apr 8, 2024
Merged
Clarify data stream recommendations and best practices#107233dakrone merged 2 commits intoelastic:mainfrom
dakrone merged 2 commits intoelastic:mainfrom
Conversation
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.
Contributor
|
Documentation preview: |
Collaborator
|
Pinging @elastic/es-docs (Team:Docs) |
Collaborator
|
Pinging @elastic/es-data-management (Team:Data Management) |
nielsbauman
approved these changes
Apr 8, 2024
Contributor
nielsbauman
left a comment
There was a problem hiding this comment.
LGTM, 1 minor comment but overall I think this should remove even more doubts people might have.
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.
Collaborator
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
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.