[jira] [Commented] (AIRFLOW-815) Add previous/next execution dates to available default variables.

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AIRFLOW-815:
---------------------------------------------------------

Commit a67e4390d2217dd0fdc3429e943cdc6c552fac73 in incubator-airflow's branch refs/heads/v1-8-test from [~danielvdende]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=a67e439 ]

[AIRFLOW-815] Add prev/next execution dates to template variables

This patch adds the previous/next execution dates
to the default variables available in a template.

Closes #2033 from danielvdende/add-execution-dates


> Add previous/next execution dates to available default variables.
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-815
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-815
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core, models
>            Reporter: Daniel van der Ende
>            Assignee: Daniel van der Ende
>            Priority: Minor
>             Fix For: 1.8.1
>
>
> Due to the way the Airflow scheduler works (i.e.  job instance is started once the period it covers has ended), in cases where you want to use the execution date in DAG tasks, the execution date will be 'off by one' (that is, it will be off by one period). In order to work around this, it would be nice if we could add previous/next execution date to the default variables available in templates (http://pythonhosted.org/airflow/code.html#default-variables)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)