[
https://issues.apache.org/jira/browse/HDFS-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045688#comment-13045688
]
Aaron T. Myers commented on HDFS-2045:
--------------------------------------
bq. I'm sorry, I read too fast. Are you just proposing to fix the
hdfs-config.sh?
Unfortunately, I think it would take more than that to restore the previous
behavior. Since the jars, etc are now located based solely on the single
HADOOP_PREFIX env var, one cannot have separate distribution directories for
HDFS, MR, and Common.
My main issue is that all of this rearranging/reworking of the tarball and
development layouts were done under the auspices of adding RPM support. I'll be
honest and say that I didn't review the RPM work hardly at all, because I
assumed from the title that it would not affect tarballs or the dev
environment. Had there been separate JIRAs along the lines of "rearrange the
layout of distribution builds" and "add RPM support", I likely would have
reviewed the former.
> 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
