utkarsharma2 commented on PR #31662: URL: https://github.com/apache/airflow/pull/31662#issuecomment-1573117591
@uranusjr While going through the code I found there are two other tooltips where we show the operator name https://github.com/apache/airflow/blob/29d2a31dc04471fc92cbfb2943ca419d5d8a6ab0/airflow/www/static/js/task_instances.js#L111 and https://github.com/apache/airflow/blob/29d2a31dc04471fc92cbfb2943ca419d5d8a6ab0/airflow/www/static/js/task_instances.js#L170 Ideally, both of them should show values derived from `custom_operator_name` but only the base operator has the `operator_name` property and not the task instance object. In both of the instance as mentioned above, we are displaying values of `ti.operator` which are populated from `task_type` of operator. https://github.com/apache/airflow/blob/29d2a31dc04471fc92cbfb2943ca419d5d8a6ab0/airflow/models/taskinstance.py#L888 since `self.operator` is getting used at multiple places in code, I think we should create another property in the task instance operator similar to `operator_name` in the base operator and use that while displaying in UI. WDYT? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
