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

Doug Cutting commented on HADOOP-2404:
--------------------------------------

> that leaves us with 9 methods.

Okay, I trust your math.  9 it is.

> And 27 files that directly read "fs.default.name". So the change is not hard 
> its just massive.

But not destabilizing.  Replacing calls to conf.get("fs.default.name") with a 
call to a static method that does pretty much the same thing but is 
back-compatible seems safe enough.  0.16 is not yet frozen.

> all changes are born to be removed in the next release

That I don't see.  Won't we still want all of these methods in the next 
release?  We might add more validation to them, and add more such methods, and 
perhaps call them earlier, to force early validation, but we'll still want the 
methods, no?

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