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

Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2022/09/21 02:46:00 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

lincoln lee closed FLINK-17141.
-------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> Name of SQL Operator is too long
> --------------------------------
>
>                 Key: FLINK-17141
>                 URL: https://issues.apache.org/jira/browse/FLINK-17141
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Wenlong Lyu
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>             Fix For: 1.15.0
>
>
> 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.20.10#820010)