[
https://issues.apache.org/jira/browse/FLINK-21765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-21765:
----------------------------
Fix Version/s: 1.19.0
(was: 1.18.0)
> Remove implementation-specific MetricGroup parents
> --------------------------------------------------
>
> Key: FLINK-21765
> URL: https://issues.apache.org/jira/browse/FLINK-21765
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Metrics
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned,
> stale-assigned, starter
> Fix For: 1.19.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.20.10#820010)
