[
https://issues.apache.org/jira/browse/HADOOP-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089576#comment-13089576
]
Ravi Prakash commented on HADOOP-7563:
--------------------------------------
Maybe this is too late and perhaps it needs a new JIRA but while we are at it,
can we please get rid of the ugly for loops for populating jar files into
CLASSPATH?
http://download.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
. If we only included <directory>/* , all the jars under that directory will be
picked up. Why did we have to write these for loops?
> hadoop-config.sh setup HADOOP_HDFS_HOME and HADOOP_MAPRED_HOME incorrectly
> --------------------------------------------------------------------------
>
> Key: HADOOP-7563
> URL: https://issues.apache.org/jira/browse/HADOOP-7563
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.23.0
> Reporter: Eric Yang
> Assignee: Eric Yang
> Fix For: 0.23.0
>
> Attachments: HADOOP-7563-1.patch, HADOOP-7563.patch
>
>
> HADOOP_HDFS_HOME and HADOOP_MAPRED_HOME was set to
> HADOOP_PREFIX/share/hadoop/hdfs and HADOOP_PREFIX/share/hadoop/mapreduce.
> This setup confuses the location of hdfs and mapred scripts. Instead the
> script should look for hdfs and mapred script in HADOOP_PREFIX/bin.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
