Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Wed, 21 Oct 2015 07:26:27 +0000 (UTC)
From: "Akira AJISAKA (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12506454.1304714324000.14890.1445412387751@Atlassian.JIRA>
In-Reply-To: <JIRA.12506454.1304714324000@Atlassian.JIRA>
References: <JIRA.12506454.1304714324000@Atlassian.JIRA>
 <JIRA.12506454.1304714324422@arcas>
Subject: [jira] [Commented] (HADOOP-7266) Deprecate metrics v1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Akira AJISAKA commented on HADOOP-7266:
---------------------------------------

I don't think it's good idea to commit a patch that adds warnings and then commit another patch that fixes the warnings. I'd like to keep the source code clean in any revision.

If we are to add warnings in this issue, we will 
* deprecate metrics1 and then remove metrics1 in trunk,
* deprecate metrics1 and then fix javac warnings in branch-2.

I'm thinking it is simpler to
* deprecate metrics1 and then remove metrics1 in trunk,
* deprecate metrics1 in branch-2.

> Deprecate metrics v1
> --------------------
>
>                 Key: HADOOP-7266
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7266
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 2.8.0
>            Reporter: Luke Lu
>            Assignee: Akira AJISAKA
>            Priority: Blocker
>         Attachments: HADOOP-7266-remove.001.patch, HADOOP-7266.001.patch, HADOOP-7266.002.patch, HADOOP-7266.003.patch, HADOOP-7266.004.patch, HADOOP-7266.005.patch
>
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)