flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Flink Jira Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-21765) Remove implementation-specific MetricGroup parents
Date Sun, 27 Jun 2021 22:39:02 GMT

     [ https://issues.apache.org/jira/browse/FLINK-21765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Flink Jira Bot updated FLINK-21765:
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community
manage its development. I see this issues has been marked as Major but is unassigned and neither
itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major"
to the issue". If this ticket is a Major, please either assign yourself or give an update.
Afterwards, please remove the label or in 7 days the issue will be deprioritized.

> 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
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>             Fix For: 1.14.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

View raw message