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

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

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

AIRFLOW-168 Correct evaluation of @once schedule

If the schedule @once was used with a start_date two dagruns
would be created as next_run_date would be none and compared
against dag.start_date. This patch fixes that by returning
immediately if a dagrun has already occured with an @once
schedule.


> schedule_interval @once scheduling dag atleast twice
> ----------------------------------------------------
>
>                 Key: AIRFLOW-168
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-168
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: Airflow 1.7.1.2
>            Reporter: Sumit Maheshwari
>            Assignee: Bolke de Bruin
>         Attachments: Screen Shot 2016-05-24 at 9.51.50 PM.png, 
> screenshot-1.png
>
>
> I was looking at example_xcom example and found that it got scheduled twice. 
> Ones at the start_time and ones at the current time. To be correct I tried 
> multiple times (by reloading db) and its same. 
> I am on airflow master, using sequential executor with sqlite3. Though it 
> works as expected on a prod env which is running v1.7 with celery workers and 
> mysql backend.  



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

Reply via email to