[
https://issues.apache.org/jira/browse/HADOOP-12467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radhey updated HADOOP-12467:
----------------------------
Description:
Currently, on Windows the hadoop wrapper script (hadoop-config.cmd) assumes its
the only place that uses JAVA_LIBRARY_PATH and initializes it to a blank line.
set JAVA_LIBRARY_PATH=
This prevents anyone from setting this outside of the hadoop wrapper (say
hadoop-config.cmd) for their own native libraries.
The fix is pretty simple. Don't initialize it to '' and append the native libs
like normal.
was:
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.
> Windows Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH
> ----------------------------------------------------------------------------
>
> Key: HADOOP-12467
> URL: https://issues.apache.org/jira/browse/HADOOP-12467
> Project: Hadoop Common
> Issue Type: Bug
> Components: scripts
> Affects Versions: 2.6.0
> Reporter: Radhey
> Assignee: Radhey
> Priority: Minor
> Labels: JAVA_LIBRARY_PATH, Windows
>
> Currently, on Windows the hadoop wrapper script (hadoop-config.cmd) assumes
> its the only place that uses JAVA_LIBRARY_PATH and initializes it to a blank
> line.
> set JAVA_LIBRARY_PATH=
> This prevents anyone from setting this outside of the hadoop wrapper (say
> hadoop-config.cmd) for their own native libraries.
> The fix is pretty simple. Don't initialize it to '' and append the native
> libs like normal.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
