You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Robert Chansler (JIRA)" <ji...@apache.org> on 2008/10/21 21:54:44 UTC
[jira] Updated: (HADOOP-3730) add new JobConf constructor that
disables loading default configurations
[ https://issues.apache.org/jira/browse/HADOOP-3730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Chansler updated HADOOP-3730:
------------------------------------
Release Note: Added a JobConf constructor that disables loading default configurations so as to take all default values from the JobTracker's configuration. (was: Adds a new JobConf constructor that disables loading default configurations. This can be used to take all default values from the JobTracker's configuration.)
> add new JobConf constructor that disables loading default configurations
> ------------------------------------------------------------------------
>
> Key: HADOOP-3730
> URL: https://issues.apache.org/jira/browse/HADOOP-3730
> Project: Hadoop Core
> Issue Type: New Feature
> Environment: all
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 0.19.0
>
> Attachments: patch3730.txt, patch3730.txt, patch3730.txt
>
>
> Similar to the {{Configuration(boolean loadDefauls)}} , {{JobConf}} should have such constructor.
> This would allow supporting default values on the JT side as the client would not submit its default values in the job.xml.
> It would address Hadoop-3287
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.