[
https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chad Metcalf updated HADOOP-6453:
---------------------------------
Attachment: HADOOP-6453.trunk.patch
Its been a long week. This moved to hadoop-config in a post split world. This
problem exists in trunk and 20.x.
There are no tests, its a wrapper script. Doesn't change the default behavior
except for the unlikely case where people were setting JAVA_LIBRARY_PATH and it
was getting stomped on and when its no longer stomped on they'll break. Very
unlikely case.
> 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.1
> Reporter: Chad Metcalf
> Priority: Minor
> Fix For: 0.20.2
>
> 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.
