[
https://issues.apache.org/jira/browse/MAPREDUCE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744449#action_12744449
]
Amareshwari Sriramadasu commented on MAPREDUCE-849:
---------------------------------------------------
Configuration properties in Mapreduce project are be catagorized into the
following and suggested name for each catagory.
||Catagory|| Suggested Name||
|Cluster config | mapreduce.* |
|JobTracker config | mapreduce.jobtracker.* |
|TaskTracker config | mapreduce.tasktracker.* |
|Job-level config | mapreduce.job.* |
|Task-level config | mapreduce.task.* |
|Map task config | mapreduce.map.* |
|Reduce task config | mapreduce.reduce.* |
|Job client config | mapreduce.jobclient.* |
|Pipes config | mapreduce.pipes.* |
|Lib config | mapreduce.<libname>.* |
|Example config | mapreduce.<example-name>.* |
|Test config | mapreduce.test.* |
|Streaming config | mapreduce.streaming.* or streaming.*|
|Contrib project config | mapreduce.<contrib-project>.* or <contrib-project>.* |
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
>
>
> 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.
