potiuk commented on issue #22006: URL: https://github.com/apache/airflow/issues/22006#issuecomment-2495765414
> It is silly to call strange, unnatural, or niche, a scenario where code is updated and is incompatible with the previous version. It's called a breaking change, happens all the time. Not when you have alternative where you can keep consistency between versions. As already explained - with DAG versioning Airlfow will be able to run existing wokflows with old code and new workflows with new code. There is no need to pause anything - it is going to **just** work. Airlfow's tasks are idempotent, which also mean that if you manage code consistency in DAG run, theoretically (and practically) data in one DAG Run should not interfere with Data in another DAG Run - and they could be run in parallel, This way you achieve exactly the same as with your proposed pausing, but ... without pausing. The pausing scenario you described is only really needed in "regular" cases because of current Airlfow 2 defficiency - lack of ability of linking a version of a DAG code with particular DAG run. DAG versioning is going to change it. You are likely quite a bit too much rooted with current limitations of Airflow 2 - that are going to go away. I don't think it's silly - simply you are talking about a workaround and I am talking about a completely new feature that solves the problem differently. -- 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]
