You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Andrey (JIRA)" <ji...@apache.org> on 2017/05/05 15:31:04 UTC

[jira] [Created] (FLINK-6464) Metric name is not stable

Andrey created FLINK-6464:
-----------------------------

             Summary: Metric name is not stable
                 Key: FLINK-6464
                 URL: https://issues.apache.org/jira/browse/FLINK-6464
             Project: Flink
          Issue Type: Bug
    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.3.15#6346)