[jira] [Comment Edited] (FLINK-20375) Support to control operator name in SQL

["Ada Wong (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252560#comment-17252560 ] 

Ada Wong edited comment on FLINK-20375 at 1/18/22, 2:44 AM:
------------------------------------------------------------

My temporary fix for prometheus memory problem, it is not the best practice.

!image-2020-12-21-09-48-17-845.png!


was (Author: ana4):
My temporary fix for prometheus memory problem, it is not the best practice.代码占位符

!image-2020-12-21-09-48-17-845.png!

> Support to control operator name in SQL
> ---------------------------------------
>
>                 Key: FLINK-20375
>                 URL: https://issues.apache.org/jira/browse/FLINK-20375
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API, Table SQL / Planner
>            Reporter: hailong wang
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>         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.20.1#820001)