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

Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/04/15 02:19:00 UTC

[jira] [Commented] (FLINK-17141) Name of SQL Operator is too long

    [ https://issues.apache.org/jira/browse/FLINK-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083740#comment-17083740 ] 

Jark Wu commented on FLINK-17141:
---------------------------------

Is there a better way for this? For example, introduce a new mechanism to use operator id for logging. 

I would like to keep the original name in web ui. Because if we cut the operator name, we may lose some useful information when troubleshooting.

> Name of SQL Operator is too long
> --------------------------------
>
>                 Key: FLINK-17141
>                 URL: https://issues.apache.org/jira/browse/FLINK-17141
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: Wenlong Lyu
>            Priority: Major
>
> the name of the operator contains the detail logic of the operator, which make it very large when there are a lot of columns. It is a disaster for logging and web ui, also can cost a lot of memory because we use the name widely such as ExecutionVertex and failover message etc.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)