Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 16 May 2017 22:36:04 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13072536.1494958564000.225813.1494974164085@Atlassian.JIRA>
In-Reply-To: <JIRA.13072536.1494958564000@Atlassian.JIRA>
References: <JIRA.13072536.1494958564000@Atlassian.JIRA> <JIRA.13072536.1494958564205@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-18060) Backport to branch-1 HBASE-9774
 HBase native metrics and metric collection for coprocessors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 16 May 2017 22:36:12 -0000


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

Enis Soztutar commented on HBASE-18060:
---------------------------------------

I think you have identified the main issues nicely. Some of the new APIs are using JDK-8 features that have to be rethought of. Some un-sugaring is needed. Most of the changes are in the new modules, so I won't be too much concerned about them. The harder parts to backport would be at the DW -> hadoop metrics2 integration layer I think. However, if we do this backport, it will make it easier for further patches that uses the new framework to be backported. 

> Backport to branch-1 HBASE-9774 HBase native metrics and metric collection for coprocessors
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18060
>                 URL: https://issues.apache.org/jira/browse/HBASE-18060
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 1.4.0, 1.3.2, 1.5.0
>            Reporter: Vincent Poon
>            Assignee: Vincent Poon
>
> I'd like to explore backporting HBASE-9774 to branch-1, as the ability for coprocessors to report custom metrics through HBase is useful for us, and if we have coprocessors use the native API, a re-write won't be necessary after an upgrade to 2.0.
> The main issues I see so far are:
> - the usage of Java 8 language features.  Seems we can work around this as most of it is syntactic sugar.  Will need to find a backport for LongAdder
> - dropwizard 3.1.2 in Master.  branch-1 is still on yammer metrics 2.2.  Not sure if these can coexist just for this feature


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)