hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11983) HADOOP_USER_CLASSPATH_FIRST works the opposite of what it is supposed to do
Date Tue, 26 May 2015 15:39:18 GMT

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

Sangjin Lee commented on HADOOP-11983:
--------------------------------------

[~aw], could you take a quick look at it? Thanks!

> HADOOP_USER_CLASSPATH_FIRST works the opposite of what it is supposed to do
> ---------------------------------------------------------------------------
>
>                 Key: HADOOP-11983
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11983
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.0.0
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>         Attachments: HADOOP-11983.001.patch
>
>
> The behavior of HADOOP_USER_CLASSPATH_FIRST works the opposite of what it should do.
If it is not set, HADOOP_CLASSPATH is prepended. If set, it is appended.
> You can easily try out by doing something like
> {noformat}
> HADOOP_CLASSPATH=/Users/alice/tmp hadoop classpath
> {noformat}
> (HADOOP_CLASSPATH should point to an existing directory)
> I think the if clause in hadoop_add_to_classpath_userpath is reversed.
> This issue seems specific to the trunk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message