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 "Luke Lu (Created) (JIRA)" <ji...@apache.org> on 2011/10/13 20:21:11 UTC

[jira] [Created] (HADOOP-7742) Evolve metrics2 in 0.23 and trunk to allow coexistence with 0.20-security releases

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
             Fix For: 0.23.0


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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (HADOOP-7742) Evolve metrics2 in 0.23 and trunk to allow coexistence with 0.20-security releases

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated HADOOP-7742:
----------------------------

    Fix Version/s:     (was: 0.24.0)
    
> 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

[jira] [Commented] (HADOOP-7742) Evolve metrics2 in 0.23 and trunk to allow coexistence with 0.20-security releases

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
    [ 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

[jira] [Updated] (HADOOP-7742) Evolve metrics2 in 0.23 and trunk to allow coexistence with 0.20-security releases

Posted by "Harsh J (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Harsh J updated HADOOP-7742:
----------------------------

    Target Version/s: 3.0.0  (was: 0.23.0)
    
> 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