You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "jack (Jira)" <ji...@apache.org> on 2019/11/05 16:30:00 UTC
[jira] [Commented] (AIRFLOW-3242) execution_date for
TriggerDagRunOperator should be based from Triggering dag
[ https://issues.apache.org/jira/browse/AIRFLOW-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16967657#comment-16967657 ]
jack commented on AIRFLOW-3242:
-------------------------------
[~zhoufengzd] do you still experience the issue? I worked with backfill and TriggerDagRunOperator and didn't experience this problem.
> execution_date for TriggerDagRunOperator should be based from Triggering dag
> ----------------------------------------------------------------------------
>
> Key: AIRFLOW-3242
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3242
> Project: Apache Airflow
> Issue Type: Bug
> Components: DagRun
> Affects Versions: 1.8.2, 1.9.0, 1.10.0
> Environment: any linux / mac os
> Reporter: Feng Zhou
> Priority: Major
>
> TriggerDagRunOperator should pick up execute_date from context instead just default to today. This broke back filling logic if TriggerDagRunOperator is used.
> Could simply add one line to address this issue, see red highlighted line below:
> def execute(self, context):
> ....
> dr = trigger_dag.create_dagrun(
> run_id=dro.run_id,
> state=State.RUNNING,
> *_{color:#FF0000}execution_date=context['execution_date'],{color}_* ## around line#70
> conf=dro.payload,
> external_trigger=True)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)