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

Chesnay Schepler updated FLINK-7957:
------------------------------------
    Fix Version/s:     (was: 1.5.0)

> Add MetricGroup#getLogicalScope
> -------------------------------
>
>                 Key: FLINK-7957
>                 URL: https://issues.apache.org/jira/browse/FLINK-7957
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>    Affects Versions: 1.4.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Trivial
>
> Various reporters make use of a generalized scope string (e.g. 
> "taskmanager.job.task.<metricname>"). This string can be generated with 
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As 
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup<AbstractMetricGroup<?>>)group).getLogicalScope(CHARACTER_FILTER,
>  '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the 
> MetricGroup interface.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to