airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angel Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AIRFLOW-957) the execution_date of dagrun that is created by TriggerDagRunOperator is not euqal the execution_date of TriggerDagRunOperator's task instance
Date Wed, 12 Apr 2017 10:52:41 GMT

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

Angel Fernandez reassigned AIRFLOW-957:
---------------------------------------

    Assignee: Angel Fernandez

> the execution_date of dagrun that is created by TriggerDagRunOperator is not euqal the
execution_date of TriggerDagRunOperator's task instance
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-957
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-957
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>            Reporter: Calvin Wang
>            Assignee: Angel Fernandez
>
> The execution_date of Dagrun that be created by TriggerDagRunOperator  is triggered time.
When I rerun a dag that execution_date is a past time(e.g. 20160101), the execution_date of
external dag that trigger by TriggerDagRunOperator  is current time(e.g. 20170309). I expect
execution_date is a past time(e.g. 20160101) . Why TriggerDagRunOperator doesn't provide the
exection_date option at the beginning? Is there anything wrong in this way?



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

Mime
View raw message