[
https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795044#action_12795044
]
Steve Loughran commented on HADOOP-6453:
----------------------------------------
I don't use the startup scripts, so it doesn't have any effect to me, but I see
the benefit for anyone who has native libs they do want in the runtime.
# There is a risk that this will break things, namely any system that has a
JAVA_LIBRARY_PATH env variable set to something that is incompatible with
HADOOP. This is the usual badly-configured CLASSPATH problem, the reason a lot
of java launcher scripts either ignore that env variable completely, or provide
some way to disable it (e.g. Ant's -noclasspath option)
# Even if there is no automated test, someone needs to manually check that if
the existing value of JAVA_LIBRARY_PATH is set to something with spaces in,
such as c:\Program Files\some application\ then everything still propagates
correctly. As usual, Cygwin will be the troublespot here.
> 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
> Affects Versions: 0.20.2, 0.21.0, 0.22.0
> Reporter: Chad Metcalf
> Assignee: Chad Metcalf
> Priority: Minor
> Fix For: 0.20.2, 0.21.0, 0.22.0
>
> Attachments: HADOOP-6453-0.20.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.
-
You can reply to this email to add a comment to the issue online.
