Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 11 Oct 2012 10:33:03 +0000 (UTC)
From: "John Gordon (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <689190278.25523.1349951583121.JavaMail.jiratomcat@arcas>
In-Reply-To: <1107384818.157717.1349237047837.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HADOOP-8874) HADOOP_HOME and -Dhadoop.home (from
 hadoop wrapper script) are not uniformly handled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Gordon updated HADOOP-8874:
--------------------------------

    Attachment: fix_home.patch

This patch adds a consistency layer for HADOOP_HOME lookups and provides abstractions to qualify bin paths of hadoop binary components.
                
> HADOOP_HOME and -Dhadoop.home (from hadoop wrapper script) are not uniformly handled
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8874
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8874
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: scripts, security
>    Affects Versions: 1-win
>         Environment: Called from external process with -D flag vs HADOOP_HOME set.
>            Reporter: John Gordon
>              Labels: security
>             Fix For: 1-win
>
>         Attachments: fix_home.patch
>
>
> There is a -D flag to set hadoop.home, which is specified in the hadoop wrapper scripts.  This is particularly useful if you want SxS execution of two or more versions of hadoop (e.g. rolling upgrade).  However, it isn't honored at all.  HADOOP_HOME is used in 3-4 places to find non-java hadoop components such as schedulers, scripts, shared libraries, or with the Windows changes -- binaries.
> Ideally, these should all resolve the path in a consistent manner, and callers shuold have a similar onus applied when trying to resolve an invalid path to their components.  This is particularly relevant to scripts or binaries that may have security impact, as absolute path resolution is generally safer and more stable than relative path resolution.

--
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