[
https://issues.apache.org/jira/browse/AIRFLOW-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132976#comment-17132976
]
ASF GitHub Bot commented on AIRFLOW-6704:
-----------------------------------------
yuqian90 commented on pull request #7324:
URL: https://github.com/apache/airflow/pull/7324#issuecomment-642451211
> @yuqian90 : Thank You ! for your response.
> If so be the case then just wondering the same code with `execution_date`
works perfectly fine with the earlier version of Airflow that we are using i.e.
v1.10.2. If the `dagrun_operator` construct changed, I could not get any
literature about that.
Many things changed between 10.2 and 10.10. I haven't looked too carefully
into the error you have. I can't tell if this PR is related. Any reason you
think this PR is the cause?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> TaskInstance.operator is not set when task is marked success or failed in the
> Web UI
> ------------------------------------------------------------------------------------
>
> Key: AIRFLOW-6704
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6704
> Project: Apache Airflow
> Issue Type: Bug
> Components: models
> Affects Versions: 1.10.7
> Reporter: Qian Yu
> Assignee: Qian Yu
> Priority: Major
> Fix For: 1.10.10
>
>
> {{TaskInstance.operator}} is currently only set when task is executed. But if
> a task is marked success or failed, the {{operator}} field is left as
> {{None}}.
> This causes bugs when some code tries to use the operator field to find the
> name of the class.
> The fix is trivial, just set {{TaskInstance.operator}} in its constructor.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
