You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/07 10:40:00 UTC
[jira] [Updated] (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 ]
Flink Jira Bot updated FLINK-17141:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was: auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)