Cherry-pick "Backup schema keys in incremental backups" into 1.2 release#5158
Merged
martinmr merged 1 commit intorelease/v1.2from Apr 10, 2020
Merged
Cherry-pick "Backup schema keys in incremental backups" into 1.2 release#5158martinmr merged 1 commit intorelease/v1.2from
martinmr merged 1 commit intorelease/v1.2from
Conversation
The full schema should be backed up during incremental backups. During restore, the schema should be cleared before processing each backup to end up with only the final schema.
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
1 participant
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.
Cherry-pick #5147.
The full schema should be backed up during incremental backups.
During restore, the schema should be cleared before processing each backup
to end up with only the final schema.
This change is
Docs Preview: