hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-813) Document and likewise implement relevant checks/escape functions for what form of input is acceptable for setting up a container launch context i.e. special chars in resource names, env vars and the commands
Date Fri, 14 Jun 2013 00:43:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hitesh Shah moved MAPREDUCE-3155 to YARN-813:
---------------------------------------------

                 Tags:   (was: mr2,mapreduce-2.0)
          Component/s:     (was: mrv2)
                       nodemanager
        Fix Version/s:     (was: 0.24.0)
    Affects Version/s:     (was: 0.23.0)
                       2.0.4-alpha
                       0.23.8
                  Key: YARN-813  (was: MAPREDUCE-3155)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
    
> Document and likewise implement relevant checks/escape functions for what form of input
is acceptable for setting up a container launch context i.e. special chars in resource names,
env vars and the commands
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-813
>                 URL: https://issues.apache.org/jira/browse/YARN-813
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 0.23.8, 2.0.4-alpha
>            Reporter: Hitesh Shah
>
> What should a user of yarn escape/not escape when passing in input for the container
launch contexts 
>   - localized resources' names are used to create symlinks. 
>     - Are special chars supported in symlinks or do they need to be escaped? 
>   - Likewise for environment variables and commands. 
> Current implementation uses a shell script to setup the environment and launch the commands.
What should the user be aware of when setting up the launch context? The input also should
be such that a user should not need to change code based on what platform or flavor of shell
is being used to setup the env and run the commands. 

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

Mime
View raw message