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

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

Commit f69eec3b44cbb0a0fb46a17baec195f7f3baf50e in incubator-airflow's branch 
refs/heads/master from [~bolke]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=f69eec3 ]

[AIRFLOW-68] Align start_date with the schedule_interval

This particular issue arises because of an alignment issue between
start_date and schedule_interval. This can only happen with cron-based
schedule_intervals that describe absolute points in time (like “1am”) as
opposed to time deltas (like “every hour”)

In the past (and in the docs) we have simply said that users must make
sure the two params agree. But this is counter intuitive. As in these
cases, start_date is sort of like telling the scheduler to
“start paying attention” as opposed to “this is my first execution date”.

This patch changes the behavior of the scheduler. The next run date of
the dag will be treated as "start_date + interval" unless the start_date
is on the (previous) interval in which case the start_date will be the
next run date.


> Align start_date with the schedule_interval
> -------------------------------------------
>
>                 Key: AIRFLOW-68
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-68
>             Project: Apache Airflow
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: Airflow 1.7.1
>            Reporter: Bolke de Bruin
>             Fix For: Airflow 1.8
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to