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] Updated: (MAPREDUCE-849) Renaming of configuration property names in mapreduce
Date Sat, 19 Sep 2009 03:00:15 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sharad Agarwal updated MAPREDUCE-849:
-------------------------------------

    Release Note: Rename and categorize configuration keys into - cluster, jobtracker, tasktracker,
job, client. Constants are defined for all keys in java and code is changed to use constants
instead of direct strings. All old keys are deprecated except of examples and tests. The change
is incompatible because support for old keys is not provided for config keys in examples.

> 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, patch-849-1.txt, patch-849-2.txt,
patch-849-3.txt, patch-849.txt
>
>
> 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