hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13364) Variable HADOOP_LIBEXEC_DIR must be quoted in bin/hadoop line 26
Date Wed, 03 May 2017 00:25:04 GMT

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

Allen Wittenauer commented on HADOOP-13364:

For the record, spaces in paths can't be fixed without HADOOP-13365.  There is way way way
too much dependence on using space as a parameter delimiter.

> Variable HADOOP_LIBEXEC_DIR must be quoted in bin/hadoop line 26
> ----------------------------------------------------------------
>                 Key: HADOOP-13364
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13364
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 2.6.4
>         Environment: Linux, Unix, Mac machines with spaces in file paths
>            Reporter: Jeffrey McAteer
>              Labels: script
>             Fix For: 3.0.0-alpha1
>   Original Estimate: 1m
>  Remaining Estimate: 1m
> Upon a standard download, untaring, and execution of './hadoop-2.6.4/bin/hadoop version',
I received: './hadoop-2.6.4/bin/hadoop: line 26: /Users/jeffrey/Projects/Hadoop: No such file
or directory'
> My project directory was called 'Hadoop Playground', with a space in it. Upon investigating,
I found line 26 held:
> . $HADOOP_LIBEXEC_DIR/hadoop-config.sh
> Which means the variable $HADOOP_LIBEXEC_DIR will be handled as multiple arguments if
there is a space. The solution is to quote the variable, like so:
> . "$HADOOP_LIBEXEC_DIR/hadoop-config.sh"

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message