Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <1299259337.47901267495085872.JavaMail.jira@brutus.apache.org>
Date: Tue, 2 Mar 2010 01:58:05 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6604) Improve HADOOP_HOME detection and
 handling in hadoop-config
In-Reply-To: <1014627972.47391267493765810.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer commented on HADOOP-6604:
------------------------------------------

This patch breaks if any hadoop core jar is in .. rather than the one we care about. 


> Improve HADOOP_HOME detection and handling in hadoop-config
> -----------------------------------------------------------
>
>                 Key: HADOOP-6604
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6604
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.20.2
>            Reporter: Chad Metcalf
>            Assignee: Chad Metcalf
>            Priority: Minor
>         Attachments: HADOOP-6604.patch
>
>
> If HADOOP_HOME is not set by the time hadoop-config is sourced we should try to guess it. Generally speaking hadoop-config.sh is in bin and HADOOP_HOME should generally be .. from there. Additionally we can do some verification of this guess by looking for jars in HADOOP_HOME.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.