Docs: Clarify index downgrade limitations in snapshot compatibility matrix - #7615
Open
jiwan67 wants to merge 1 commit into
Open
Docs: Clarify index downgrade limitations in snapshot compatibility matrix#7615jiwan67 wants to merge 1 commit into
jiwan67 wants to merge 1 commit into
Conversation
…atrix ## Summary This PR resolves a logical contradiction in the Snapshot Version Compatibility matrix in the `snapshot-and-restore.md` documentation. ## Issue Details The text below the compatibility table explicitly states: > "You can’t restore an index to an earlier version of Elasticsearch. For example, you can’t restore an index created in 8.18.0 to a cluster running 8.15.0." However, because minor versions are grouped together in the table (e.g., `8.0-8.19`), the `✅` in the matrix technically implies that an 8.19 index could be restored to an 8.0 cluster, which contradicts the rule. ## Changes - Added a new footnote (`^3^`) to the `8.0-8.19` row. - Provided a footnote description explicitly stating that restoring to an earlier minor version within the same major version is not supported. This ensures the table remains compact while preventing user confusion regarding minor version downgrades.
|
❌ Author of the following commits did not sign a Contributor Agreement: Please, read and sign the above mentioned agreement if you want to contribute to this project |
Contributor
|
@jiwan67 , the diff of the PR looks like a full file rewrite because the line endings were converted to CRLF. Could you normalize the file back to LF (as on main), then commit and push again? Then we can review the footnote update. I agree with the contradiction you've shared but I'd suggest something different. |
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
2 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.
Summary
This PR resolves a logical contradiction in the Snapshot Version Compatibility matrix in the
snapshot-and-restore.mddocumentation.Issue Details
The text below the compatibility table explicitly states:
However, because minor versions are grouped together in the table (e.g.,
8.0-8.19), the✅in the matrix technically implies that an 8.19 index could be restored to an 8.0 cluster, which contradicts the rule.Changes
^3^) to the8.0-8.19row.This ensures the table remains compact while preventing user confusion regarding minor version downgrades.