[
https://issues.apache.org/jira/browse/HBASE-18060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022188#comment-16022188
]
Andrew Purtell commented on HBASE-18060:
----------------------------------------
While running the test suite for branch-1 locally I get the below at step
maven-remote-resources-plugin:1.5:process (aggregate-licenses) @ hbase-assembly
:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(aggregate-licenses) on project hbase-assembly: Error rendering velocity
resource. Error invoking method 'get(java.lang.Integer)' in java.util.ArrayList
at META-INF/LICENSE.vm[line 1678, column 8]: InvocationTargetException: Index:
0, Size: 0 -> [Help 1]
{noformat}
Did not investigate why. supplemental-models.xml on branch-1 needs adjustment?
TestReplicasClient flaked. Not related to the change as far as I can tell.
{noformat}
Flaked tests:
org.apache.hadoop.hbase.client.TestReplicasClient.testCancelOfMultiGet(org.apache.hadoop.hbase.client.TestReplicasClient)
Run 1: TestReplicasClient.testCancelOfMultiGet:585 null
Run 2: PASS
{noformat}
> 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
> Attachments: HBASE-18060.branch-1.3.v1.patch,
> HBASE-18060.branch-1.3.v2.patch, HBASE-18060.branch-1.3.v3.patch,
> HBASE-18060.branch-1.3.v4.patch, HBASE-18060.branch-1.3.v5.patch,
> HBASE-18060.branch-1.v1.patch, HBASE-18060.branch-1.v2.patch,
> HBASE-18060.branch-1.v3.patch, HBASE-18060.branch-1.v4.patch,
> HBASE-18060.branch-1.v5.patch
>
>
> 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)
