hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chuan Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9599) hadoop-config.cmd doesn't set JAVA_LIBRARY_PATH correctly
Date Sat, 25 May 2013 01:03:20 GMT

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

Chuan Liu commented on HADOOP-9599:

Judging from the context, I think it should be HADOOP_COMMON_HOME instead of HADOOP_HOME.
Because the purpose of the script is mainly to include JNI library, i.e. native library, in
Java library path, and native library is a hadoop-common project.
I think it is also good to add some comments as well.
> hadoop-config.cmd doesn't set JAVA_LIBRARY_PATH correctly
> ---------------------------------------------------------
>                 Key: HADOOP-9599
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9599
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>         Environment: Windows
>            Reporter: Mostafa Elhemali
>            Assignee: Mostafa Elhemali
>         Attachments: HADOOP-9599.patch
> In Windows, hadoop-config.cmd uses the non-existent-variable HADOOP_CORE_HOME when setting
the JAVA_LIBRAR_PATH variable. It should use HADOOP_HOME.
> The net effect is that running e.g. "hdfs namenode" would error out with UnsatisfiedLinkError
because it can't access hadoop.dll.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message