hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2045) HADOOP_*_HOME environment variables no longer work for tar ball distributions
Date Wed, 15 Jun 2011 02:20:47 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049576#comment-13049576

Aaron T. Myers commented on HDFS-2045:

In the absence of compatibility concerns, I agree with option 2. I'm sorry we didn't go with
this in the first place.

That said, I don't feel strongly about maintaining the backward compatibility of this "feature"
of being able to run Hadoop from distinct mr/hdfs/common build directories.

So, if no one else feels strongly about this, then I'm fine rolling with option 2 (and closing
this issue.)

> HADOOP_*_HOME environment variables no longer work for tar ball distributions
> -----------------------------------------------------------------------------
>                 Key: HDFS-2045
>                 URL: https://issues.apache.org/jira/browse/HDFS-2045
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Aaron T. Myers
> It used to be that you could do the following:
> # Run `ant bin-package' in your hadoop-common checkout.
> # Set HADOOP_COMMON_HOME to the built directory of hadoop-common.
> # Run `ant bin-package' in your hadoop-hdfs checkout.
> # Set HADOOP_HDFS_HOME to the built directory of hadoop-hdfs.
> # Set PATH to have HADOOP_HDFS_HOME/bin and HADOOP_COMMON_HOME/bin on it.
> # Run `hdfs'.
> \\
> \\
> As of HDFS-1963, this no longer works since hdfs-config.sh is looking in HADOOP_COMMON_HOME/bin/
for hadoop-config.sh, but it's being placed in HADOOP_COMMON_HOME/libexec.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message