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

feat: TTL for fuse table #7828

Open
Tracked by #7823
BohuTANG opened this issue Sep 23, 2022 · 5 comments
Open
Tracked by #7823

feat: TTL for fuse table #7828

BohuTANG opened this issue Sep 23, 2022 · 5 comments
Labels
C-feature Category: feature

Comments

@BohuTANG
Copy link
Member

BohuTANG commented Sep 23, 2022

Summary

Segment Level TTL to expire the data。
optimize table t1 purge will:

  1. check the TTL of the table
  2. purge the segments and blocks if they are expired
@BohuTANG BohuTANG added the C-feature Category: feature label Sep 23, 2022
@BohuTANG BohuTANG added the good first issue Category: good first issue label Jan 15, 2023
@caibirdme
Copy link

any update for this feature?

@BohuTANG BohuTANG removed the good first issue Category: good first issue label Mar 29, 2024
@BohuTANG
Copy link
Member Author

@caibirdme Hi, no update yet.

Since Databend uses object storage, which is cheaper than local disk, space isn't an issue, and there is a vacuum command(the storage space will reclaim if data is deleted or a table is dropped):
https://docs.databend.com/sql/sql-commands/ddl/table/vacuum-table

Future plans to adjust this remain undecided.

@caibirdme
Copy link

in vacuum-table doc, there's a setting DATA_RETENTION_TIME_IN_DAYS , is it a global setting? How can I make this setting vary from table to table? And is this user's task to run vaccum table routinely?

@TCeason
Copy link
Collaborator

TCeason commented Mar 30, 2024

in vacuum-table doc, there's a setting DATA_RETENTION_TIME_IN_DAYS , is it a global setting? How can I make this setting vary from table to table? And is this user's task to run vaccum table routinely?

Yes it's a global setting now. Maybe cc @lichuang can provide help

@BohuTANG
Copy link
Member Author

in vacuum-table doc, there's a setting DATA_RETENTION_TIME_IN_DAYS , is it a global setting? How can I make this setting vary from table to table? And is this user's task to run vaccum table routinely?

We are planning to add this option to table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature Category: feature
Projects
None yet
Development

No branches or pull requests

3 participants