hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-6491) Environment variable handling assumes values should be appended
Date Thu, 14 Sep 2017 16:22:00 GMT

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

Allen Wittenauer commented on MAPREDUCE-6491:

a) DYLD_LIBRARY_PATH should be in the list
b)  As mentioned several times, this won't work if a job (e.g., streaming) calls the shell
scripts with the default values.

> 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: MAPREDUCE-6491.011.patch, YARN-2369-10.patch, YARN-2369-1.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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message