Update DagVersion instead of stamping new one if there are no DAG runs using that version #45524
Open
1 task done
Labels
AIP-65: DAG history in UI
area:MetaDB
Meta Database related issues.
kind:meta
High-level information important to the community
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
The text was updated successfully, but these errors were encountered: