hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dustin Cote (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6491) Environment variable handling assumes values should be appended
Date Mon, 05 Oct 2015 09:04:27 GMT

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

Dustin Cote commented on MAPREDUCE-6491:

That all makes pretty good sense to me.  I'd like to propose the following:
1) we keep HADOOP_CLASSPATH as appendable in branch-2 to keep things working as they are now
on that branch
2) we open up a JIRA to take HADOOP_CLASSPATH off of the appendable list for trunk
3) in trunk, we keep HADOOP_CLASSPATH as a replaceable variable that gets turned into HADOOP_TASK_CLASSPATH
for the app framework (not sure if this needs a JIRA)

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

This message was sent by Atlassian JIRA

View raw message