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

implements --partitions=db.table:part_name1,part_name2 and --partitions=db2.table2:* to allow more flexible backup logic #916

Closed
Slach opened this issue May 7, 2024 · 1 comment
Assignees
Milestone

Comments

@Slach
Copy link
Collaborator

Slach commented May 7, 2024

create, upload, download, restore command should support it for regular and embedded backup aproach

@Slach Slach self-assigned this May 7, 2024
@Slach Slach added this to the 2.6.0 milestone May 7, 2024
@minguyen9988
Copy link
Contributor

thanks, this will make it much easier to do partial backup.

@Slach Slach modified the milestones: 2.6.0, 2.5.9 May 13, 2024
@Slach Slach changed the title implements --partitions=table:part_name1,part_name2,table2:* to allow more flexible backup logic implements --partitions=db.table:part_name1,part_name2,db2.table2:* to allow more flexible backup logic May 14, 2024
@Slach Slach changed the title implements --partitions=db.table:part_name1,part_name2,db2.table2:* to allow more flexible backup logic implements --partitions=db.table:part_name1,part_name2' and '--partitions=db2.table2:* to allow more flexible backup logic May 14, 2024
@Slach Slach changed the title implements --partitions=db.table:part_name1,part_name2' and '--partitions=db2.table2:* to allow more flexible backup logic implements --partitions=db.table:part_name1,part_name2 and --partitions=db2.table2:* to allow more flexible backup logic May 14, 2024
@Slach Slach closed this as completed in 186b4f1 May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants