You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/01/28 22:36:44 UTC

[jira] Commented: (MAPREDUCE-2242) LinuxTaskController doesn't properly escape environment variables

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

Todd Lipcon commented on MAPREDUCE-2242:
----------------------------------------

Talked to Arun about this today - apparently this will be fixed as part of MAPREDUCE-2178.
So we can ignore this for a bit if people are OK with tests failing in the meantime.

> LinuxTaskController doesn't properly escape environment variables
> -----------------------------------------------------------------
>
>                 Key: MAPREDUCE-2242
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2242
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task-controller
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: mapreduce-2242.txt
>
>
> LinuxTaskController currently just writes "export FOO=bar" pairs into taskjvm.sh, which fails if the value has multiple words or contains a space. This is causing TestDebugScriptWithLinuxTaskController among others to fail on trunk with the following message:
> {code}
> export: 1: -Dhadoop.tasklog.iscleanup: bad variable name
> {code}
> since it generated a taskjvm.sh including the following:
> {code}
> export HADOOP_CLIENT_OPTS=-Dhadoop.tasklog.taskid=attempt_20110104180935141_0001_m_000001_0 -Dhadoop.tasklog.iscleanup=false -Dhadoop.tasklog.totalLogFileSize=0
> {code}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.