[
https://issues.apache.org/jira/browse/FLINK-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17240713#comment-17240713
]
Jark Wu commented on FLINK-20388:
---------------------------------
[~chesnay], however, if we generate a shorter name for the operator name, then
maybe lot's of operator will have the same name. It's hard to distinguish the
operators in Web UI.
You can see the discussion in FLINK-20375.
"Why would we want users to explicitly set the operator name for metrics"
This can be a public API of DataStream, but SQL will generate the metric name
automantically (by using a shorter name with id), and keep the operator name
with full information.
> Supports users setting operators' metrics name
> ----------------------------------------------
>
> Key: FLINK-20388
> URL: https://issues.apache.org/jira/browse/FLINK-20388
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream, Runtime / Metrics
> Reporter: hailong wang
> Priority: Major
>
> Currently, we only support users setting operators name.
> And we use those in the topology to distinguish operators, at the same time,
> as the operator metrics name.
> If the operator name length is larger than 80, we truncate it simply.
> I think we can allow users to set operator metrics name like operators name.
> If the user is not set, use the current way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
