You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Angel Fernandez (JIRA)" <ji...@apache.org> on 2017/04/12 10:52:41 UTC

[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

     [ 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)