[
https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252560#comment-17252560
]
Mulan Wong edited comment on FLINK-20375 at 12/21/20, 1:48 AM:
---------------------------------------------------------------
My temporary fix, it is not the best practice.代码占位符
!image-2020-12-21-09-48-17-845.png!
was (Author: ana4):
My temporary fix, it is not best practice.
> 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
> Attachments: image-2020-12-21-09-48-17-845.png
>
>
> 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)
