[ https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan updated HADOOP-6453: -------------------------------- Status: Open (was: Patch Available) Fix Version/s: 0.22.0 The trunk patch has unfortunately gone stale. However, this seems like a good change to make with essentially no risk. This will treat JAVA_LIBRARY_PATH consistently with JAVA_HOME, and can be marked as incompatible change. cygwin should be fine. Chad, can you please spin up a new patch and, barring any objections, I'll review and commit it. > 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.22.0 > > Attachments: HADOOP-6453-0.20.patch, HADOOP-6453-0.20v2.patch, > HADOOP-6453-trunkv2.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.