[ https://issues.apache.org/jira/browse/MAPREDUCE-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16434021#comment-16434021 ]
Jason Lowe commented on MAPREDUCE-7069: --------------------------------------- Given this is XML and not HTML I think we should avoid the use of HTML tags for now. Those tags will make it harder to read if the consumer is not viewing it with an HTML viewer. For the mapred-default.xml descriptions I think we just need to mention that variables can also be specified as separate properties and give a simple example demonstrating the syntax. > 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 > 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 > > > 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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: mapreduce-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: mapreduce-issues-h...@hadoop.apache.org