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

Update DagVersion instead of stamping new one if there are no DAG runs using that version #45524

Open
1 task done
jedcunningham opened this issue Jan 9, 2025 · 0 comments
Labels
AIP-65: DAG history in UI area:MetaDB Meta Database related issues. kind:meta High-level information important to the community

Comments

@jedcunningham
Copy link
Member

Body

We should only keep around DAG versions that have a corresponding run. I believe the easy answer is to allow DAGs to update in place, without stamping a new version, if there are no runs on that version.

We should be careful of race conditions while we are at it.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.
@jedcunningham jedcunningham added kind:meta High-level information important to the community AIP-65: DAG history in UI labels Jan 9, 2025
@dosubot dosubot bot added the area:MetaDB Meta Database related issues. label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AIP-65: DAG history in UI area:MetaDB Meta Database related issues. kind:meta High-level information important to the community
Projects
None yet
Development

No branches or pull requests

1 participant