You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ultrabug (JIRA)" <ji...@apache.org> on 2017/07/18 15:06:00 UTC

[jira] [Updated] (AIRFLOW-1424) Add a next_scheduler_run property to DAGs

     [ https://issues.apache.org/jira/browse/AIRFLOW-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ultrabug updated AIRFLOW-1424:
------------------------------
    Attachment: add_next_scheduler_run_property.patch
                258d7101c452_add_next_scheduler_run_field_to_dag.py

> Add a next_scheduler_run property to DAGs
> -----------------------------------------
>
>                 Key: AIRFLOW-1424
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1424
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: DAG
>            Reporter: Ultrabug
>         Attachments: 258d7101c452_add_next_scheduler_run_field_to_dag.py, add_next_scheduler_run_property.patch
>
>
> The scheduler's DAG run creation logic can be tricky and one is easily confused with the start_date + interval and period end scheduling way of thinking.
> It would ease airflow's usage to add a **next_scheduler_run** property to DAGs so that we can very easily see the (un)famous **period end** after which the scheduler will create a new DAG run for our workflows.
> These patches add such a field to the **dag** table and the DagModel property + scheduler logic to update it when calculated.
> I will attach patches and make a github PR.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)