potiuk commented on issue #23776: URL: https://github.com/apache/airflow/issues/23776#issuecomment-1131687492
Indeed that's an interesting side-effect. We do not have DAG versioning implemented yet https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-36+DAG+Versioning so those kind of problems are expected. As described in https://airflow.apache.org/docs/apache-airflow/stable/index.html > Workflows are expected to be mostly static or slowly changing. You can think of the structure of the tasks in your workflow as slightly more dynamic than a database structure would be. Airflow workflows are expected to look similar from a run to the next, this allows for clarity around unit of work and continuity. We have currently no mechanisms to track version changes for DAGs, so if you do such structural changes, you might expect not only backfill to not work but also UI displays to be misleading. That's what DAG versioning (hopefully we will approve and start implementing on it soon) should address. Currently, the recommendation is to copy DAGs to another dag in case of structural changes like that. -- 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]
