[test](regression) Add backup/restore DB case#26312
Merged
dataroaring merged 1 commit intoapache:masterfrom Nov 2, 2023
Merged
[test](regression) Add backup/restore DB case#26312dataroaring merged 1 commit intoapache:masterfrom
dataroaring merged 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
run buildall |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
768313d to
f622137
Compare
Contributor
Author
|
run buildall |
Contributor
|
PR approved by at least one committer and no changes requested. |
xiaokang
pushed a commit
that referenced
this pull request
Nov 3, 2023
* [feature](backup) add property to remove snapshot before creating repo (#25847) Doris is not responsible for managing snapshots, but it needs to clear all snapshots before doing backup/restore regression testing, so a property is added to indicate that existing snapshots need to be cleared when creating a repo. In addition, a regression test case for backup/restore has been added. * [cases](regression-test) Add backup & restore with multi tables test (#26040) * [cases](regression-test) Add backup restore operation test (#26169) 1. restore overwrites an exists table 2. backup & restore with exclude table 3. restore to a new table 4. restore mix exists and new tables 5. restore with alias * [fix](regression) Add auto-expired prefix for backup/restore cases (#26272) * [test](regression) Add backup/restore DB case (#26312)
dutyu
pushed a commit
to dutyu/doris
that referenced
this pull request
Nov 4, 2023
seawinde
pushed a commit
to seawinde/doris
that referenced
this pull request
Nov 8, 2023
seawinde
pushed a commit
to seawinde/doris
that referenced
this pull request
Nov 13, 2023
gnehil
pushed a commit
to gnehil/doris
that referenced
this pull request
Dec 4, 2023
* [feature](backup) add property to remove snapshot before creating repo (apache#25847) Doris is not responsible for managing snapshots, but it needs to clear all snapshots before doing backup/restore regression testing, so a property is added to indicate that existing snapshots need to be cleared when creating a repo. In addition, a regression test case for backup/restore has been added. * [cases](regression-test) Add backup & restore with multi tables test (apache#26040) * [cases](regression-test) Add backup restore operation test (apache#26169) 1. restore overwrites an exists table 2. backup & restore with exclude table 3. restore to a new table 4. restore mix exists and new tables 5. restore with alias * [fix](regression) Add auto-expired prefix for backup/restore cases (apache#26272) * [test](regression) Add backup/restore DB case (apache#26312)
XuJianxu
pushed a commit
to XuJianxu/doris
that referenced
this pull request
Dec 14, 2023
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
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.
Proposed changes
Issue Number: close #xxx
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...