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 933A417585 for ; Fri, 8 May 2015 18:21:01 +0000 (UTC) Received: (qmail 60677 invoked by uid 500); 8 May 2015 18:21:01 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 60637 invoked by uid 500); 8 May 2015 18:21:01 -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 60615 invoked by uid 99); 8 May 2015 18:21:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2015 18:21:01 +0000 Date: Fri, 8 May 2015 18:21:01 +0000 (UTC) From: "Roman Shaposhnik (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-11393) Revert HADOOP_PREFIX, go back to HADOOP_HOME 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-11393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535161#comment-14535161 ] Roman Shaposhnik commented on HADOOP-11393: ------------------------------------------- The patch is pretty straightforward and in general looks good to me. A couple of comments still: * the parts that patch documentation need to be rebased on the current state of trunk * the hadoop-functions.sh part needs to be rebased as well * httpfs-env.sh httpfs-config.sh httpfs.sh mapred-config.sh rumen2sls.sh still use HADOOP_PREFIX even after applying the patch The biggest question I have is re: overriding HADOOP_HOME with HADOOP_PREFIX unconditionally. Shouldn't we at least start issuing a deprecation warning for use of HADOOP_PREFIX ? [~aw] do you want to take care of the above? > Revert HADOOP_PREFIX, go back to HADOOP_HOME > -------------------------------------------- > > Key: HADOOP-11393 > URL: https://issues.apache.org/jira/browse/HADOOP-11393 > Project: Hadoop Common > Issue Type: Improvement > Affects Versions: 3.0.0 > Reporter: Allen Wittenauer > Labels: BB2015-05-TBR > Attachments: HADOOP-11393-00.patch > > > Today, Windows and parts of the Hadoop source code still use HADOOP_HOME. The switch to HADOOP_PREFIX back in 0.21 or so didn't really accomplish what it was intended to do and only helped confuse the situation. > _HOME is a much more standard suffix and is, in fact, used for everything in Hadoop except for the top level project home. I think it would be beneficial to use HADOOP_HOME in the shell code as the Official(tm) variable, still honoring HADOOP_PREFIX if it is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)