michaelmicheal commented on issue #29321: URL: https://github.com/apache/airflow/issues/29321#issuecomment-1418455335
As I understand it, as part of DAG processing, when the scheduler sees new a definition for an existing DAG, it overwrites regardless of the path. While this is by design, my team's stakeholders face this quite a bit where user's have duplicate files, with slightly different versions of a DAG. It's not obvious, and if you rely on a GCS or S3 DAG bucket that is abstracted from users/developers, it can be hard to diagnose. One solution could be: If the DAG processor sees an existing DAG defined in a file under a different path, we re-process the file under the old path, and see if the DAG is still defined there. If the DAG is still defined under the old path, we add an import error. Feel free to assign this to me. -- 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]
