[ 
https://issues.apache.org/jira/browse/AIRFLOW-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703795#comment-16703795
 ] 

ASF GitHub Bot commented on AIRFLOW-3091:
-----------------------------------------

aoen closed pull request #3925: [AIRFLOW-3091]Deactivate inactive DAGs after 
collecting DagBag
URL: https://github.com/apache/incubator-airflow/pull/3925
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/airflow/models.py b/airflow/models.py
index 1e4949e563..6c40fc5c72 100755
--- a/airflow/models.py
+++ b/airflow/models.py
@@ -272,6 +272,7 @@ def __init__(
                 'example_dags')
             self.collect_dags(example_dag_folder)
         self.collect_dags(dag_folder)
+        self.deactivate_inactive_dags()
 
     def size(self):
         """


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Deactivate inactive DAG in collecting DagBag
> --------------------------------------------
>
>                 Key: AIRFLOW-3091
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3091
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: ui, webserver
>    Affects Versions: 1.8.1, 1.8.2, 1.9.0, 1.10.0
>            Reporter: Yi Wei
>            Assignee: Yi Wei
>            Priority: Minor
>
> Airflow still displays all DAGs in admin UI, despite the fact that many DAGs 
> are already inactive. We should clean them up to avoid potential confusion.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to