-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[feature](backup) add property to remove snapshot before creating repo #25847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature](backup) add property to remove snapshot before creating repo #25847
Conversation
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
morningman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please also update the doc
fe/fe-core/src/main/java/org/apache/doris/backup/Repository.java
Outdated
Show resolved
Hide resolved
fe/fe-core/src/main/java/org/apache/doris/common/util/S3URI.java
Outdated
Show resolved
Hide resolved
01647d5 to
beb6394
Compare
beb6394 to
50487b1
Compare
|
run buildall |
morningman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
88e05d8 to
12120d9
Compare
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
12120d9 to
91f9159
Compare
|
run buildall |
25d4327 to
f75555f
Compare
|
run buildall |
JackDrogon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
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.
f75555f to
43a6d94
Compare
|
run buildall |
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
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.
* [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)
* [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)
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.
…itory delete_if_exists is a temporary solution introduced in apache#25847, to avoid concurrent testing conflicts.
…itory delete_if_exists is a temporary solution introduced in apache#25847, to avoid concurrent testing conflicts. Cherry-pick apache#38190
…itory delete_if_exists is a temporary solution introduced in apache#25847, to avoid concurrent testing conflicts. Cherry-pick apache#38190
…itory (apache#38194) delete_if_exists is a temporary solution introduced in apache#25847, to avoid concurrent testing conflicts. Cherry-pick apache#38190
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. This property is only used during testing and should not be exposed to users.
In addition, a regression test case for backup/restore has been added.
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...