Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59C5A10782 for ; Mon, 20 Jan 2014 09:15:30 +0000 (UTC) Received: (qmail 78407 invoked by uid 500); 20 Jan 2014 09:15:29 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 78085 invoked by uid 500); 20 Jan 2014 09:15:26 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 78003 invoked by uid 99); 20 Jan 2014 09:15:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jan 2014 09:15:22 +0000 Date: Mon, 20 Jan 2014 09:15:22 +0000 (UTC) From: "Harsh J (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-8061) Back port trunk metrics2 changes to 1.x branch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876270#comment-13876270 ] Harsh J commented on HADOOP-8061: --------------------------------- Is this still valid? May we close out? > Back port trunk metrics2 changes to 1.x branch > ---------------------------------------------- > > Key: HADOOP-8061 > URL: https://issues.apache.org/jira/browse/HADOOP-8061 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics > Affects Versions: 1.0.0 > Reporter: Luke Lu > > For hysterical raisins, metrics2 code in hadoop 1.x branch and trunk diverged. It looks like HBase needs to support both 1.x and 0.23+ for a while, hence the more urgent need to clean up the situation. -- This message was sent by Atlassian JIRA (v6.1.5#6160)