hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hong Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1805) Document configurations parameters that are read by MapReduce framework and cannot be changed per job
Date Thu, 20 May 2010 20:07:18 GMT

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

Hong Tang commented on MAPREDUCE-1805:
--------------------------------------

+1. Maybe we should think about a naming scheme such that the property name would identify
itself as a client-side property, framework property, library property, or application property.

> Document configurations parameters that are read by MapReduce framework and cannot be
changed per job
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1805
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1805
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.20.2
>         Environment: All
>            Reporter: Milind Bhandarkar
>
> From the documentation in mapred-default.xml, it is not apparent whether the configurations
parameters (such as mapred.tasktracker.map.tasks.maximum) can be specified per-job, or whether
these parameters are read by the framework at start-up and can never be changed. It would
be helpful to annotate the default configurations file with this information.

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


Mime
View raw message