[
https://issues.apache.org/jira/browse/MAPREDUCE-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942739#comment-14942739
]
Dustin Cote commented on MAPREDUCE-6491:
----------------------------------------
[~aw] in the context of whether HADOOP_CLASSPATH should be a variable that is
appended to (which is the default behavior for all environment variables prior
to this JIRA), do you think it should not be appended to by default? If that's
the case, then we should be changing that test case for
TestMRApps#testSetClasspathWithArchives to not rely on the appending behavior.
Are you saying we should be adding HADOOP_TASK_CLASSPATH as an appendable
variable by default and take out HADOOP_CLASSPATH from the list?
> Environment variable handling assumes values should be appended
> ---------------------------------------------------------------
>
> Key: MAPREDUCE-6491
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6491
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 2.2.0
> Reporter: Jason Lowe
> Assignee: Dustin Cote
> Attachments: YARN-2369-1.patch, YARN-2369-10.patch,
> YARN-2369-2.patch, YARN-2369-3.patch, YARN-2369-4.patch, YARN-2369-5.patch,
> YARN-2369-6.patch, YARN-2369-7.patch, YARN-2369-8.patch, YARN-2369-9.patch
>
>
> When processing environment variables for a container context the code
> assumes that the value should be appended to any pre-existing value in the
> environment. This may be desired behavior for handling path-like environment
> variables such as PATH, LD_LIBRARY_PATH, CLASSPATH, etc. but it is a
> non-intuitive and harmful way to handle any variable that does not have
> path-like semantics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
