[jira] [Updated] (AIRFLOW-1424) Make the next execution date of DAGs visible

["Ultrabug (JIRA)" <ji...@apache.org>]

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

Ultrabug updated AIRFLOW-1424:
------------------------------
    Description: 
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 execution field 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 are a simple way to implement this on the DAG model
and make use of this in the interface.

Screenshots are on the github PR.

  was:
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.

        Summary: Make the next execution date of DAGs visible  (was: Add a next_scheduler_run property to DAGs)

> Make the next execution date of DAGs visible
> --------------------------------------------
>
>                 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 execution field 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 are a simple way to implement this on the DAG model
> and make use of this in the interface.
> Screenshots are on the github PR.



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