[
https://issues.apache.org/jira/browse/FLINK-22162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17317507#comment-17317507
]
Chesnay Schepler commented on FLINK-22162:
------------------------------------------
If the operator name length limitation is impacting your setup then I'd
recommend to switch to operator IDs instead. This is not a behavior that I'd
like to be configurable because it can easily break setups if used in the wrong
way, and the supposed need for it is just a symptom of a larger issue of
operator names being way too long.
> Make Max Operator name Length Configurable
> ------------------------------------------
>
> Key: FLINK-22162
> URL: https://issues.apache.org/jira/browse/FLINK-22162
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Lu Niu
> Priority: Minor
> Labels: pull-request-available
>
> MaxOperatorNameLength is hardcoded to be 80. User might want to tune the
> parameter so that after exposing metrics to external metrics system, user can
> better query the metrics data by name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
