You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Harsh J (JIRA)" <ji...@apache.org> on 2012/09/22 10:44:08 UTC
[jira] [Commented] (HADOOP-7742) Evolve metrics2 in 0.23 and trunk
to allow coexistence with 0.20-security releases
[ https://issues.apache.org/jira/browse/HADOOP-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461073#comment-13461073 ]
Harsh J commented on HADOOP-7742:
---------------------------------
Hi Luke,
So this is an "incompatible change" now? What would we need to do to help projects such as HBase at this time?
> Evolve metrics2 in 0.23 and trunk to allow coexistence with 0.20-security releases
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-7742
> URL: https://issues.apache.org/jira/browse/HADOOP-7742
> Project: Hadoop Common
> Issue Type: Improvement
> Components: metrics
> Affects Versions: 0.23.0
> Reporter: Luke Lu
> Labels: metrics
>
> HADOOP-7734 expressed the desire to support downstream projects that depends on both 0.23+ and 0.20-security releases.
> In order to achieve that we need to evolve the 0.23/trunk API a little to avoid name conflicts:
> # Rename AbstractMetric to ImmutableMetric, which also address a common question sink implementer ask about thread safety.
> # Rename MetricsRecord to ImmutableMetrics, ditto.
> # Rename MetricsVisitor to MetricVisitor.
> We better do it before 0.23 is released or, it will be an "incompatible" change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira