Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 3 Nov 2014 20:07:34 +0000 (UTC)
From: "Masatake Iwasaki (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12752243.1414880197000.401256.1415045254495@Atlassian.JIRA>
In-Reply-To: <JIRA.12752243.1414880197000@Atlassian.JIRA>
References: <JIRA.12752243.1414880197000@Atlassian.JIRA>
 <JIRA.12752243.1414880197575@arcas>
Subject: [jira] [Commented] (HADOOP-11257) Deprecate 'hadoop jar'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Masatake Iwasaki commented on HADOOP-11257:
-------------------------------------------

The problem seems to be that {{hadoop jar}} (partially) works for mapred and yarn apps because classpath setting for {{hadoop}} command includes all of common, hdfs, mapred and yarn libs. How about showing warnings if the env var which is only handled by {{mapred}} or {{yarn}} command is set?

> Deprecate 'hadoop jar'
> ----------------------
>
>                 Key: HADOOP-11257
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11257
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Allen Wittenauer
>
> Given that 'hadoop jar' and 'yarn jar' work differently, we should mark 'hadoop jar' as deprecated in 2.7 and remove it in trunk.


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