[
https://issues.apache.org/jira/browse/MAPREDUCE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748315#action_12748315
]
Amareshwari Sriramadasu commented on MAPREDUCE-849:
---------------------------------------------------
I propose, we add following interfaces for cluster configuration keys
{code}
public Interface org.apache.hadoop.mapreduce.Configs {
// holding cluster level configs keys.
}
public Interface org.apache.hadoop.mapreduce.server.jobtracker.JTConfigs {
// holding jobtracker config keys
}
public Interface org.apache.hadoop.mapreduce.server.tasktracker.TTConfigs {
// holding tasktracker config keys
}
{code}
All job-level keys will be added to org.apache.hadoop.mapreduce.JobContext as
public static String.
These new names will be used everywhere in the framework.
Thoughts?
> Renaming of configuration property names in mapreduce
> -----------------------------------------------------
>
> Key: MAPREDUCE-849
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-849
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Fix For: 0.21.0
>
> Attachments: Config changes.xls, Config changes.xls
>
>
> In-line with HDFS-531, property names in configuration files should be
> standardized in MAPREDUCE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
