airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dud (JIRA)" <>
Subject [jira] [Created] (AIRFLOW-39) DagRun scheduled after end_date
Date Tue, 03 May 2016 10:49:12 GMT
dud created AIRFLOW-39:

             Summary: DagRun scheduled after end_date
                 Key: AIRFLOW-39
             Project: Apache Airflow
          Issue Type: Wish
         Environment: -  Airflow version: v1.7.0
-  Airflow components: webserver and scheduler with a postgres database and LocalExecutor
-  Python Version: 2.7.9

            Reporter: dud
            Priority: Minor


When I write a new DAG, it is automatically picked by the scheduler as intended. However the
end_date parameter is not accounted when creating a DagRun, so that DagRuns scheduled after
end_date are being displayed in the web interface and are staying in the running state forever
as the scheduler doesn't launch them.

>From my reading of the sources, the end_date paremeter is not used when creating a DagRun.

Is there any reason for this behaviour ?


This message was sent by Atlassian JIRA

View raw message