[
https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239345#comment-17239345
]
Jark Wu edited comment on FLINK-20375 at 11/26/20, 4:55 PM:
------------------------------------------------------------
Yes. That's true.
An better idea is that runtime could separate the operator-name and the
operator-metric-name (both can be defined by users).
And Web UI can show both on the topology graph.
Neverless, this needs some support from runtime and we should create another
issue for that.
was (Author: jark):
Yes. That's true.
An better idea is that runtime could separate the operator-name and the
operator-metric-name (both can be defined by users).
And Web UI can should both on the topology graph.
Neverless, this needs some support from runtime and we should create another
issue for that.
> 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)
