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

Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/03/13 12:10:00 UTC

[jira] [Created] (FLINK-21765) Remove implementation-specific MetricGroup parents

Chesnay Schepler created FLINK-21765:
----------------------------------------

             Summary: Remove implementation-specific MetricGroup parents
                 Key: FLINK-21765
                 URL: https://issues.apache.org/jira/browse/FLINK-21765
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / Metrics
            Reporter: Chesnay Schepler
            Assignee: Chesnay Schepler
             Fix For: 1.13.0


MetricGroups currently form a bi-directly graph, usually with explicit requirements that type the parent must have. For example, an OperatorMG has a hard requirement that the parent is a TaskMG.

As a result they are quite inflexible, which particular shows in tests, as you can't just create one metric group, but have to build an entire tree.

The end goal of this ticket is to remove AbstractMetricGroup#parent, and along the way we'll decouple the various MG implementations from each other.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)