release-20.1: backupccl: add is_full_cluster to SHOW BACKUP #46768
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
Full cluster restores can only be performed on full cluster backups. Therefore, it is useful if SHOW BACKUP can tell the user if a given backup is a full cluster backup or not. Release note (enterprise change): SHOW BACKUP now shows whether a BACKUP is a full cluster backup or not. Release justification: low risk, high impact change to existing functionality.
|
This change is |
dt
approved these changes
Mar 31, 2020
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.
Backport 1/1 commits from #45860.
/cc @cockroachdb/release
Full cluster restores can only be performed on full cluster backups.
Therefore, it is useful if SHOW BACKUP can tell the user if a given
backup is a full cluster backup or not.
Closes #44813.
Release note (enterprise change): SHOW BACKUP now shows whether a BACKUP
is a full cluster backup or not.
Release justification: low risk, high impact change to existing
functionality.