[ https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239524#comment-17239524 ]
hailong wang commented on FLINK-20375: -------------------------------------- Yes, I think this a good way. For if we just keep the one, the topology graph will show the short name if we set a short name. For topology diagrams, the more complete the name, the better. But for metrics, the shorter, the better. > Add a switch to control the operator name in SQL > ------------------------------------------------ > > Key: FLINK-20375 > URL: https://issues.apache.org/jira/browse/FLINK-20375 > Project: Flink > Issue Type: Improvement > Components: Table SQL / Runtime > Reporter: hailong wang > Priority: Major > > From the user-zh email: > [http://apache-flink.147419.n8.nabble.com/FlinkSQL-Prometheus-td8858.html] > The sql operator name is too large, this resulted in a lot of memory in > querying Prometheus which is not friendly in the production environment. > > I think we can add a switch to control the operator name in SQL. > A full name helps debug Jobs, and a short name helps to send this as metrics > which will save bandwidth, CPU consumption during compression, and downstream > storage. -- This message was sent by Atlassian Jira (v8.3.4#803005)