[
https://issues.apache.org/jira/browse/HADOOP-9450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635295#comment-13635295
]
Harsh J commented on HADOOP-9450:
---------------------------------
Mitch,
One comment though:
bq. Our problem is in the HADOOP_CONF_DIR jars. There are some JARs in there
that our customers are trying to override.
A jar will not be picked if its in a directory thats on the classpath. Classes
under package folders (such as foo/org/apache/bar.class, if "foo" is on
classpath) and other file resources may get picked up but never jars. Jars are
only picked up if they are directly placed onto the classpath (either via a
wildcard or explicitly). Might be worth checking your environment again for
whats really causing an issue.
> 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: Improvement
> Components: scripts
> Reporter: Mitch Wyle
> Assignee: Harsh J
> Fix For: 3.0.0, 1-win, 2.0.5-beta, 1.3.0
>
> Attachments: HADOOP-9450-branch-1.patch,
> HADOOP-9450-branch-1-win.patch, HADOOP-9450-branch-2.patch,
> HADOOP-9450.patch, 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
