[
https://issues.apache.org/jira/browse/FLINK-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20375:
-----------------------------------
Labels: auto-deprioritized-major stale-major (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-deprioritized-major, stale-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)
