[AIRFLOW-39] DagRun scheduled after end_date

• Type: Wish
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Environment: - Airflow version: v1.7.0; - Airflow components: webserver and scheduler with a postgres database and LocalExecutor; - Python Version: 2.7.9
• External issue URL: https://github.com/apache/incubator-airflow/pull/1466
• Assignee: Siddharth Anand
• Reporter: dud
• Created: 03/May/16 10:48
• Updated: 06/May/16 08:03
• Resolved: 05/May/16 19:09

Description

Hello

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 ?

Regards
dud