4paradigm / 4paradigm/OpenMLDB
delete pre-agg tables if user going to drop the long window deployment
- Dominant language
- C++
- Stars
- 1.7k
- Forks
- 331
- Avg merge
- 12d 12h
- Merged PRs (30d)
- 1
Description
**Bug Description**
Long window, delete the procedure after deploy, but the pre aggregated table will not be deleted.
If you create a long window with the same name and function again, you will be prompted that the pre aggregated table already exists.
**Expected Behavior**
When deleting the procedure, the pre aggregated table should be deleted at the same time.
**Steps to Reproduce**
1. create table
2. deploy one long window
3. drop procedure
4. deploy long window
Contributor guide
Research direction
Look for code that handles dropping procedures and deleting pre-aggregated tables. The issue mentions long window deployments and pre-aggregated tables. Search for terms like 'pre aggregated table', 'long window', and 'drop procedure' in the codebase. Check the SQL execution path and table lifecycle management. Verify the fix by testing the steps to reproduce: create table, deploy long window, drop procedure, and redeploy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- databases, machine-learning, sql
- Domain
- backend, databases, machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100