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

Automatic Partition Maintenance #22441

Closed
ethanzhou8109 opened this issue Jan 20, 2021 · 2 comments
Closed

Automatic Partition Maintenance #22441

ethanzhou8109 opened this issue Jan 20, 2021 · 2 comments
Labels
duplicate Issues or pull requests already exists. type/feature-request Categorizes issue or PR as related to a new feature.

Comments

@ethanzhou8109
Copy link

ethanzhou8109 commented Jan 20, 2021

Feature Request

Is your feature request related to a problem? Please describe:

Describe the feature you'd like:

For time range partitioned table, tidb does not have a mechanism to automatic drop partition after xx days and add new partition for new day (which can implemented by stored procedure and event), so how can i maintain fix days partition automatically in tidb?

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

@ethanzhou8109 ethanzhou8109 added the type/feature-request Categorizes issue or PR as related to a new feature. label Jan 20, 2021
@morgo
Copy link
Contributor

morgo commented Jan 22, 2021

I think this is a duplicate of #19132 , would you agree?

The title says "add partition automatically", but the feature request refers to INTERVAL PARTITIONING and ttl tables.

@zz-jason
Copy link
Member

Yes, I think we can track the progress in #19132

@zz-jason zz-jason added the duplicate Issues or pull requests already exists. label Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues or pull requests already exists. type/feature-request Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

3 participants