[DOCS] Data stream snapshot behavior with excluded backing indices #72761
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
danhermann
added
>docs
elasticmachine
added
Team:Data Management
|
Pinging @elastic/es-core-features (Team:Core/Features) |
|
Pinging @elastic/es-docs (Team:Docs) |
jrodewig
approved these changes
May 5, 2021
There was a problem hiding this comment.
LGTM. I left a wording suggestion, but feel free to ignore if wanted. Thanks @danhermann.
Comment on lines
65
to
70
| metadata or its other backing indices. Snapshots can also include data streams | ||
| but exclude specific backing indices. In this case, the data stream will be | ||
| restored with only the backing indices present in the snapshot. In the case | ||
| that the original write index of the data stream was not present in the | ||
| snapshot, the data stream's most recent backing index that is present in the | ||
| snapshot will become the current write index. |
There was a problem hiding this comment.
I'd break this into a separate paragraph and reword to avoid passive voice. Feel free to ignore if wanted.
Suggested change
| metadata or its other backing indices. Snapshots can also include data streams | |
| but exclude specific backing indices. In this case, the data stream will be | |
| restored with only the backing indices present in the snapshot. In the case | |
| that the original write index of the data stream was not present in the | |
| snapshot, the data stream's most recent backing index that is present in the | |
| snapshot will become the current write index. | |
| metadata or its other backing indices. | |
| Snapshots can also include a data stream but exclude specific backing indices. | |
| When you restore the data stream, it will only contain backing indices present | |
| in the snapshot. If the stream's original write index is not in the snapshot, | |
| the most recent backing index from the snapshot becomes the stream's write index. |
|
Thanks, @jrodewig! I included your suggested wording in the commit. |
chengyang14
pushed a commit
to chengyang14/elasticsearch
that referenced
this pull request
May 7, 2021
danhermann
added a commit
to danhermann/elasticsearch
that referenced
this pull request
Jun 30, 2021
danhermann
added a commit
that referenced
this pull request
Jun 30, 2021
danhermann
added a commit
to danhermann/elasticsearch
that referenced
this pull request
Jul 6, 2021
danhermann
added a commit
that referenced
this pull request
Jul 6, 2021
danhermann
added a commit
to danhermann/elasticsearch
that referenced
this pull request
Aug 18, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relates to #72747