-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
support dag level db cleanup on airflow cli #24828
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Assigned you |
Any update on this one? We would also appreciate this feature. |
FYI. This issue is > 2 years old if you have not noticed, so it's very likely there are no updates. Contributions are always welcome - and actually contributing something is the fastest way to have something implemented. So if your "any updates on this ?" means - "I would like to contribute that", then it's cool. Otherwise it does not move a needle - someone has to commit to it and implement it. Shall I assign you maybe? Or maybe you can find someone who will commit and implement it @jkbngl ? |
Description
While full db cleanup is useful to run in rare occasions, deleting data regarding to specific dag ids provides modular maintenance method to clean specific "intensive" dags and provide clear context and responsivness in the web ui and interfaces in cluster.
an initial idea was gathered to add optional
dag_id
key in_TableConfig
at db_cleanup.py and append condition in_build_query
(after adding the argument of course). Those changes could be provided also in the helm chart as list of cleanup jobs.would love to hear you inputs about the use case and the implementation relating to the current effort(e.g #24590).
Thanks.
Use case/motivation
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: