hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9450) HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
Date Sat, 13 Apr 2013 17:02:16 GMT

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

Chris Nauroth commented on HADOOP-9450:
---------------------------------------

+1 for the patch.  I tested successfully on Windows.  Thanks for the patch, Harsh!

I don't think it's important to keep the old HADOOP_CONF_DIR behavior.  As you pointed out,
other Hadoop projects like Pig have already changed to the behavior of your patch.

Shall we do a branch-1 patch too?  Mitch's comments mentioned line numbers that seem to be
for the 1.x line.
                
> HADOOP_USER_CLASSPATH_FIRST is not honored; CLASSPATH is PREpended instead of APpended
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9450
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9450
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Mitch Wyle
>         Attachments: HADOOP-9450.patch
>
>
> On line 133 of the hadoop shell wrapper, CLASSPATH is set as:
> CLASSPATH=${CLASSPATH}:${HADOOP_CLASSPATH}
> Notice that the built-up CLASSPATH, along with all the libs and unwanted JARS are pre-pended
BEFORE the user's HADOOP_CLASSPATH.  Therefore there is no way to put your own JARs in front
of those that the hadoop wrapper script sets.
> We propose a patch that reverses this order.  Failing that, we would like to add a command
line option to override this behavior and enable a user's JARs to be found before the wrong
ones in the Hadoop library paths.
> We always welcome your opinions.

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

Mime
View raw message