flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4192) Move Metrics API to separate module
Date Wed, 13 Jul 2016 12:24:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374910#comment-15374910
] 

ASF GitHub Bot commented on FLINK-4192:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2226
  
    The point of using `Properties` is that users of the API can use a class they are familiar
with and maybe even reuse configurations and tools they internally that work with `Properties`
types. Adding yet another config type means users may have to integrate yet another config
type with their own tools and utils.


> Move Metrics API to separate module
> -----------------------------------
>
>                 Key: FLINK-4192
>                 URL: https://issues.apache.org/jira/browse/FLINK-4192
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics
>    Affects Versions: 1.1.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>             Fix For: 1.1.0
>
>
> All metrics code currently resides in flink-core. If a user implements a reporter and
wants a fat jar it will now have to include the entire flink-core module.
> Instead, we could move several interfaces into a separate module.
> These interfaces to move include:
> * Counter, Gauge, Histogram(Statistics)
> * MetricGroup
> * MetricReporter, Scheduled, AbstractReporter
> In addition a new MetricRegistry interface will be required as well as a replacement
for the Configuration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message