hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6453) Hadoop wrapper script shouldn't ignore an existing JAVA_LIBRARY_PATH
Date Sun, 03 Jan 2010 19:07:54 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796016#action_12796016
] 

Steve Loughran commented on HADOOP-6453:
----------------------------------------

I think its OK as is, we just need to (currently manually) check that things work on cygwin.
To automate a command line check needs the cli tester to excec the shell scripts, which it
doesnt (yet), or use some other testrunner -antunit is the obvious choice-

> 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-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.


Mime
View raw message