Skip to content
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

[Enhancement](restore) restore table or partition with the same replication num as before the backup #11942

Merged
merged 6 commits into from
Sep 6, 2022

Conversation

nextdreamblue
Copy link
Contributor

add restore new property 'reserve_replica', which means you can
get a table with same partitions with the same replication num
as before the backup.

Proposed changes

Issue Number: close #11941

Problem summary

Describe your changes.

Checklist(Required)

  1. Does it affect the original behavior:
    • Yes
  2. Has unit tests been added:
    • No Need
  3. Has document been added or modified:
    • Yes
  4. Does it need to update dependencies:
    • No
  5. Are there any changes that cannot be rolled back:
    • No

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...

@github-actions github-actions bot added area/planner Issues or PRs related to the query planner kind/docs Categorizes issue or PR as related to documentation. labels Aug 20, 2022
@nextdreamblue nextdreamblue changed the title [Enhancement] (restore) restore table or partition with the same replication_num as before the backup [Enhancement](restore) restore table or partition with the same replication num as before the backup Aug 20, 2022
@nextdreamblue nextdreamblue changed the title [Enhancement](restore) restore table or partition with the same replication num as before the backup [Enhancement](restore) restore table or partition with the same replication num as before the backup Aug 22, 2022
@nextdreamblue nextdreamblue requested review from cambyzju and stalary and removed request for cambyzju August 25, 2022 03:33
lide-reed
lide-reed previously approved these changes Sep 1, 2022
Copy link
Contributor

@lide-reed lide-reed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

stalary
stalary previously approved these changes Sep 2, 2022
@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Sep 2, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2022

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2022

PR approved by anyone and no changes requested.

nextdreamblue and others added 6 commits September 2, 2022 09:39
add restore new property 'reserve_replica', which means you can
get a table with same partitions with the same replication num
as before the backup.
…the same replication num as before the backup

Co-authored-by: Stalary <stalary@163.com>
…the same replication num as before the backup
…eplica'

Co-authored-by: camby <104178625@qq.com>
@github-actions github-actions bot removed the approved Indicates a PR has been approved by one committer. label Sep 2, 2022
@nextdreamblue nextdreamblue requested review from morningman and lide-reed and removed request for cambyzju and morningman September 2, 2022 08:14
Copy link
Contributor

@lide-reed lide-reed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/planner Issues or PRs related to the query planner dev/merged-1.1.4 kind/docs Categorizes issue or PR as related to documentation. reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement] (restore) restore table or partition with the same replication_num as before the backup
6 participants