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

Tsz Wo (Nicholas), SZE commented on HADOOP-6123:
------------------------------------------------

{code}
+if [ -d "$HADOOP_CORE_HOME/build/ivy/lib/Hadoop-Core/common" ]; then
+for f in $HADOOP_CORE_HOME/build/ivy/lib/Hadoop-Core/common/*.jar; do
+  CLASSPATH=${CLASSPATH}:$f;
+done
+fi
{code}

The for-loop above can be eliminated by keeping the wild card (shown below) as 
what we does in the bin/hadoop script.
{code}
if [ -d "$HADOOP_CORE_HOME/build/ivy/lib/Hadoop-Core/common" ]; then
  
CLASSPATH=${CLASSPATH}:$HADOOP_CORE_HOME/build/ivy/lib/Hadoop-Core/common/*.jar;
fi
{code}

Try also the new "bin/hadoop classpath" command committed (HADOOP-5976) 
recently.

> hdfs script does not work after project split.
> ----------------------------------------------
>
>                 Key: HADOOP-6123
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6123
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.21.0
>            Reporter: Konstantin Shvachko
>             Fix For: 0.21.0
>
>         Attachments: 6123_v1.patch
>
>
> There are problems running hdfs script from common.
> # Usage message for hdfs does not have "fs" option anymore.
> # There seem to be an undocumented option "dfs", but using it throws 
> NoClassDefFoundError or ClassNotFoundException.
> # Same with other options e.g. name-node.
> May I am missing something here. How do we call ls these days?
> Do we need to move hdfs script to hdfs project.

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

Reply via email to