[FLINK-21765] Remove implementation-specific MetricGroup parents

• Type: Technical Debt
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Fix Version/s: 2.0.0
• Component/s: Runtime / Metrics
• Labels: auto-deprioritized-major auto-unassigned stale-assigned starter
• Assignee: Chesnay Schepler
• Reporter: Chesnay Schepler
• Created: 13/Mar/21 12:09
• Updated: 10/Jul/24 06:57

Description

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.

Sub-Tasks

• Remove OperatorMetricGroup#parent: Closed
• Encapsulate component meta data: Open
• JobManagerMG should not accept JobGraph: Closed
• Replace StreamTaskTestHarness#TestTaskMetricGroup: Closed
• Migrate all JobManagerMG instantiations to factory method: Closed
• Migrate all JobManagerJobMG instantiations to factory method: Closed
• Migrate all TaskManagerMG instantiations to factory method: Closed
• Migrate all TaskManagerJobMG instantiations to factory method: Closed
• Migrate all TaskMG instantiations to factory method: Closed
• Migrate all OperatorMG instantiations to factory method: Closed