Tracking: Stabilize `BACKGROUND_DDL`

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.

https://go.risingwave.com/slack

Apache License 2.0

6.78k stars 561 forks source link

Tracking: Stabilize `BACKGROUND_DDL` #16612

Open kwannoel opened 4 months ago

kwannoel commented 4 months ago

Currently background ddl has been a beta feature for a long time. It's time to make its implementation more polished. This can also simplify the code in the meta backend, so we don't have to maintain compatibility between in-memory and persisted jobs.

[ ] https://github.com/risingwavelabs/risingwave/issues/15603
[ ] Refactor sink: Instead of marking it as "finished", it should also follow the same background creation path as MV.
[ ] https://github.com/risingwavelabs/risingwave/issues/16532

github-actions[bot] commented 2 months ago

This issue has been open for 60 days with no activity.

If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.

You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄

kwannoel commented 3 weeks ago

Not urgent, wait for meta sql backend stabilized.