hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sharad Agarwal (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-849) Renaming of configuration property names in mapreduce
Date Mon, 31 Aug 2009 10:06:33 GMT

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

Sharad Agarwal commented on MAPREDUCE-849:
------------------------------------------

For cluster level properties, I would prefer mapreduce.cluster.* instead of mapreduce.* as
it won't be clear and would conflict with other namespaces. We should reserve the namespace
for framework properties - mapreduce.cluster.*, mapreduce.jobtracker.*, mapreduce.tasktracker.*,
mapreduce.client.*, mapreduce.job.* etc.

> 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.


Mime
View raw message