[
https://issues.apache.org/jira/browse/HADOOP-6919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000612#comment-13000612
]
Luke Lu commented on HADOOP-6919:
---------------------------------
bq. When revise for the current trunk (0.23), could you make sure that
MetricsContext is backward compatible? It would be good to give them sometime
in 0.23 time frame to make the switch. This ensures that HBase can release
independently, without tie to Hadoop 0.23 release schedule.
The existing 0.22+ patches don't remove but deprecate metrics v1 so existing
app depending on v1 still works (in a limited way, as they won't see metrics
defined in new metrics sources.)
This is different from the current 0.20.100 branch which removed metrics v1
completely to ensure everything was ported, as the original branch was not
targeting external/backward compatibility, which is causing some problems (with
trivial workarounds) for dependent projects like Hive that depend on metrics v1.
> Metrics2: metrics framework
> ---------------------------
>
> Key: HADOOP-6919
> URL: https://issues.apache.org/jira/browse/HADOOP-6919
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: metrics
> Affects Versions: 0.20.2
> Reporter: Luke Lu
> Assignee: Luke Lu
> Attachments: hadoop-6919-trunk-v1.patch
>
>
> The jira tracks the new metrics framework only changes, i.e., it doesn't
> track the instrumentation changes (and compatibility issues) to existing code.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
