You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "utkarsharma2 (via GitHub)" <gi...@apache.org> on 2023/06/13 12:04:56 UTC
[GitHub] [airflow] utkarsharma2 commented on a diff in pull request #31852: [Webserver] Use custom_operator_name instead of task_type in UI for taskinstance object
utkarsharma2 commented on code in PR #31852:
URL: https://github.com/apache/airflow/pull/31852#discussion_r1228015277
##########
airflow/models/taskinstance.py:
##########
@@ -886,6 +889,7 @@ def refresh_from_task(self, task: Operator, pool_override: str | None = None) ->
# value that needs to be stored in the db.
self.executor_config = task.executor_config
self.operator = task.task_type
+ self.custom_operator_name = task.operator_name
Review Comment:
I think the same thing is accomplished right now as well, since the task.operator_name handling the case of Null value at the operator class end.
But think the current approach is confusing. I'll make the change.
--
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.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org