[
https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239335#comment-17239335
]
hailong wang commented on FLINK-20375:
--------------------------------------
Thanks for your reminder [~jark], It did truncate.
But this will lead to another problem,
For the complex operators, sometimes the names are the same when truncated.
And for this, we can't tell the metrics from the operator names
> 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)
