[
https://issues.apache.org/jira/browse/FLINK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064482#comment-16064482
]
Chesnay Schepler commented on FLINK-6464:
-----------------------------------------
This is something that we should solve in general, and not rely on every single
reporter to deal with it. We should also decouple this issue with the length of
the names, as the latter is generally a reporter specific issue.
I'm not quite sure where the names are generated, but probably its either
various DataStream classes or StreamjobGraphGenerator.
For the example above, IMO the only info we actually need is
{{TumblingProcessingTimeWindow(3000, ListStateDescriptor, <TriggerClassName>)}}.
> Metric name is not stable
> -------------------------
>
> Key: FLINK-6464
> URL: https://issues.apache.org/jira/browse/FLINK-6464
> Project: Flink
> Issue Type: Bug
> Components: DataStream API, Metrics
> Affects Versions: 1.2.0
> Reporter: Andrey
>
> Currently according to the documentation
> (https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/metrics.html)
> operator metrics constructed using the following pattern:
> <operator_name>, <subtask_index>
> For some operators, "operator_name" could contain default implementation of
> toString method. For example:
> {code}
> TriggerWindow(TumblingProcessingTimeWindows(3000),
> ListStateDescriptor{serializer=org.apache.flink.api.java.typeutils.runtime.kryo.KryoSerializer@c65792d4},
> xxx.Trigger@665fe457, WindowedStream.apply(WindowedStream.java:521)) ->
> Sink: Unnamed
> {code}
> The part "@c65792d4" will be changed every time job is restarted/cancelled.
> As a consequence it's not possible to store metrics for a long time.
> Expected:
> * ensure all operators return human readable, non-default names OR
> * change the way TriggerWindow generates it's name.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
