[ 
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12560524#action_12560524
 ] 

Owen O'Malley commented on HADOOP-2404:
---------------------------------------

We've dealt with this case before in map/reduce. I propose that we add a new 
method in Configuration that is general:

{code}
/**
 * Get an integer from a list of attribute names prefering the first.
 * Should be called like:
 *   conf.getInteger(new String[]{"old.name", "new.name"}, 12);
 */
public int getInteger(String[] attribute names, int default);
{code}

Since this is generic code, it is reasonable to put it into config and it 
enables changing attribute names pretty easily. Each of the servers then has a 
single call to make to get the integer and in the next version they can drop 
the old name and move to the current getInteger.

> HADOOP-2185 breaks compatibility with hadoop-0.15.0
> ---------------------------------------------------
>
>                 Key: HADOOP-2404
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2404
>             Project: Hadoop
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.16.0
>            Reporter: Arun C Murthy
>            Assignee: Konstantin Shvachko
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: ConfigConvert.patch, ConfigConvert2.patch, 
> ConfigurationConverter.patch
>
>
> HADOOP-2185 removed the following configuration parameters:
> {noformat}
> dfs.secondary.info.port
> dfs.datanode.port
> dfs.info.port
> mapred.job.tracker.info.port
> tasktracker.http.port
> {noformat}
> and changed the following configuration parameters:
> {noformat}
> dfs.secondary.info.bindAddress
> dfs.datanode.bindAddress
> dfs.info.bindAddress
> mapred.job.tracker.info.bindAddress
> mapred.task.tracker.report.bindAddress
> tasktracker.http.bindAddress
> {noformat}
> without a backward-compatibility story.
> Lots are applications/cluster-configurations are prone to fail hence, we need 
> a way to keep things working as-is for 0.16.0 and remove them for 0.17.0.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to