[
https://issues.apache.org/jira/browse/FLINK-4210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15379258#comment-15379258
]
Stephan Ewen commented on FLINK-4210:
-------------------------------------
So, the Flink runtime metrics for an operator are in the same group as the
user's metrics? I though the user metrics were a subgroup of the operator group
- wouldn't that make sense?
Aside from that, we expose close() on so many things (like the collectors) and
it has never been an issue.
> Move close()/isClosed() out of MetricGroup interface
> ----------------------------------------------------
>
> Key: FLINK-4210
> URL: https://issues.apache.org/jira/browse/FLINK-4210
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
> Affects Versions: 1.1.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Minor
> Fix For: 1.1.0
>
>
> The (user-facing) MetricGroup interface currently exposes a close() and
> isClosed() method which generally users shouldn't need to call. They are an
> internal thing, and thus should be moved into the AbstractMetricGroup class.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
