potiuk commented on PR #59430: URL: https://github.com/apache/airflow/pull/59430#issuecomment-3677838926
> You can turn off using versioned bundles (what code is used for a task), but you cannot turn of dag versioning (keeping history of what the dag looked like). Yeah - but ....it does not result in creating a new version entry - it will just continuously override SerializedDags yeah? So generally that's something that we've been also doing in Airflow 2 and it never created huge issue (except a bit more often DB update for those ? This is what I wanted to express in this comment: > Maybe we should - by default exclude non-versioned Dags from this warning. This would be pretty much backwards-compatible for those who don't care about versioning (though I believe there is the effect of continuously overriding SerialzedDag in case of non-versioned Dags, but that is less problematic and Airflow had no problems handling it in the past. But maybe I am wrong and in such case we also create multiple versions in the DB ? Have not looked there in that detail? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
