hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Brennan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7069) Add ability to specify user environment variables individually
Date Wed, 11 Apr 2018 14:03:00 GMT

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

Jim Brennan commented on MAPREDUCE-7069:

[~jlowe], [~shanekumpf@gmail.com], thanks for the reviews!   I am working to update the
documentation and I'll put up another patch soon.
{quote}Looking at the docs generated at [http://hadoop.apache.org/docs/current/hadoop-mapreduce-client/hadoop-mapreduce-client-core/mapred-default.xml]
I'm wondering if it would be more useful to add the description for the .[var] form of the
properties to the base property instead of having separate, commented-out properties. Users
probably won't ever notice the commented-out text in that file, especially since it's buried
in a .jar when deployed, but many would notice the docs generated for properties that aren't
commented out. Thoughts?
This is what I originally started to do, but switched to the commented out option because
it felt like the descriptions were too cumbersome. But your point is well taken. I'll take
another stab at combining them. I don't see any precedent in this file for using formatting
tags inside the descriptions (<br>, <p>,...) - do you know if that is allowed?

> 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

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

View raw message