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

Weijie Guo updated FLINK-14350:
-------------------------------
    Labels: 2.0-related auto-deprioritized-major auto-deprioritized-minor 
auto-unassigned pull-request-available  (was: auto-deprioritized-major 
auto-deprioritized-minor auto-unassigned pull-request-available)

> Introduce dedicated MetricScope
> -------------------------------
>
>                 Key: FLINK-14350
>                 URL: https://issues.apache.org/jira/browse/FLINK-14350
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Metrics
>            Reporter: Chesnay Schepler
>            Priority: Not a Priority
>              Labels: 2.0-related, auto-deprioritized-major, 
> auto-deprioritized-minor, auto-unassigned, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The MetricGroup interface is currently overloaded, being used both for 
> registering groups/metrics (typically called from user-functions) and 
> accessing scope information (typically called from reporters).
> Due to effectively having 2 different audiences with different use-cases it 
> makes sense to move the scope-related methods into a separate interface.
> This should make it a lot easier to extend these interfaces, as significantly 
> less tests have to be adjusted.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to