Jason Lowe updated MAPREDUCE-7069:
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.2.0
     Release Note: 
Environment variables for MapReduce tasks can now be specified as separate 
properties, e.g.:
This form of specifying environment variables is useful when the value of an 
environement variable contains commas.
           Status: Resolved  (was: Patch Available)

Thanks to [~Jim_Brennan] for the contribution and to [~shaneku...@gmail.com] 
for additional review!  I committed this to trunk.

> Add ability to specify user environment variables individually
> --------------------------------------------------------------
>                 Key: MAPREDUCE-7069
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7069
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Jim Brennan
>            Assignee: Jim Brennan
>            Priority: Major
>             Fix For: 3.2.0
>         Attachments: MAPREDUCE-7069.001.patch, MAPREDUCE-7069.002.patch, 
> MAPREDUCE-7069.003.patch, MAPREDUCE-7069.004.patch, MAPREDUCE-7069.005.patch, 
> MAPREDUCE-7069.006.patch, MAPREDUCE-7069.007.patch
> As reported in YARN-6830, it is currently not possible to specify an 
> environment variable that contains commas via {{mapreduce.map.env}}, 
> mapreduce.reduce.env, or {{mapreduce.admin.user.env}}.
> To address this, [~aw] proposed in [YARN-6830] that we add the ability to 
> specify environment variables individually:
> {quote}e.g, mapreduce.map.env.[foo]=bar gets turned into foo=bar
> {quote}

This message was sent by Atlassian JIRA

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

Reply via email to