[
https://issues.apache.org/jira/browse/FLINK-20388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17241514#comment-17241514
]
Chesnay Schepler commented on FLINK-20388:
------------------------------------------
That sounds like excellent operator name to me.
I think the underlying issue is that we have historically been using the
operator _name_ (which, to me, is just a human-readable ID) as a form of
description, detailing every little thing (*cough* window operator *cough*).
Thus I would go in the opposite direction, and introduce a dedicated operator
description that we log once, and display in the UI when hovering or something.
I don't want us starting to have a separate naming concepts for some
components, and I think that 80 characters should be ample for a _name_.
> 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)
