utkarsharma2 opened a new issue, #41432:
URL: https://github.com/apache/airflow/issues/41432

   ### Apache Airflow version
   
   2.9.3
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Suppose we start Airflow with the following DAGs located in 
/<user_root>/airflow/dags:
   
       abc.py
       xyz.py
   
   Later, we decide to change the default DAG folder to 
/<user_root>/airflow/dags_backup/, which contains different DAG files, by 
setting the environment variable 
AIRFLOW__CORE__DAGS_FOLDER=/<user_root>/airflow/dags_backup/. After restarting 
the scheduler, the new folder includes the following DAGs:
   
       efg.py
       hij.py
   
   At this point, the Airflow UI will display all the DAGs from both sets of 
files (abc.py, xyz.py, efg.py, and hij.py), even though the current dags_folder 
no longer contains the original abc.py and xyz.py.
   
   Note: This behavior has been observed even for active DAGs.
   
   ### What you think should happen instead?
   
   The expectation is that the airflow UI should only dags belonging to the new 
dags folder `/<user_root>/airflow/dags_backup/`.
   
   ### How to reproduce
   
   1. Start Airflow with some dags in the `dags` folder.
   2. Change the default dag folder using `AIRFLOW__CORE__DAGS_FOLDER` to 
another folder containing a different set of dags. 
   3. Notice both sets of dags are visible on the UI. 
   
   ### Operating System
   
   Ventura - Mac
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to