4paradigm / 4paradigm/OpenMLDB
Support delete/gc the pre-aggregation tables when all related deployments are dropped
Open
storage-engine
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
**Describe the feature you'd like**
When deployments are dropped, there is no action for the associated pre-aggregation tables.
**Additional context**
We may maintain a counter for every pre-aggregation table. Decrease the counter when one deployment drops. When it reaches zero, users may issue a `gc` command to finally delete the tables.
Contributor guide
Research direction
Look for pre-aggregation table management and deployment lifecycle code. Understand how tables are linked to deployments and where counters could be added. The 'gc' command would need to be implemented to check counters and delete tables when zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, devops, machine-learning
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100