[
https://issues.apache.org/jira/browse/FLINK-17141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-17141:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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
>
> 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.1#820001)
