You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Tim Broberg (Commented) (JIRA)" <ji...@apache.org> on 2011/11/10 19:14:51 UTC
[jira] [Commented] (HADOOP-6453) Hadoop wrapper script shouldn't
ignore an existing JAVA_LIBRARY_PATH
[ https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147877#comment-13147877 ]
Tim Broberg commented on HADOOP-6453:
-------------------------------------
if [ -e "${HADOOP_PREFIX}/lib/libhadoop.a" ]; then
JAVA_LIBRARY_PATH=${HADOOP_PREFIX}/lib
fi
It appears that the patched script discards all other JAVA_LIBRARY_PATH definitions if there is a libhadoop.a file.
Is this by design?
> Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH
> --------------------------------------------------------------------
>
> Key: HADOOP-6453
> URL: https://issues.apache.org/jira/browse/HADOOP-6453
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.20.2, 0.21.0, 0.22.0
> Reporter: Chad Metcalf
> Assignee: Matt Foley
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: HADOOP-6453-0.20.patch, HADOOP-6453-0.20v2.patch, HADOOP-6453-0.20v3.patch, HADOOP-6453-trunkv2.patch, HADOOP-6453-trunkv3.patch, HADOOP-6453.trunk.patch
>
>
> Currently the hadoop wrapper script assumes its the only place that uses JAVA_LIBRARY_PATH and initializes it to a blank line.
> JAVA_LIBRARY_PATH=''
> This prevents anyone from setting this outside of the hadoop wrapper (say hadoop-config.sh) for their own native libraries.
> The fix is pretty simple. Don't initialize it to '' and append the native libs like normal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira