[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553196
]
Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------
I thought you proposed to get rid of "directly reading the Configuration
properties", all of them. Now I understand you do not.
Where do you count the six parameters?
A total of 14 parameters were affected by HADOOP-2185, 5 of them were removed,
that leaves us with 9 methods.
I counted at least 12 files that directly read *.http.bindAddress parameters
from the configuration.
And 27 files that directly read "fs.default.name". So the change is not hard
its just massive.
Taking into account the amount of testing, which involves old, new, and mixed
values of the parameters,
and that all changes are born to be removed in the next release, I am hesitant
whether
"establishing the precedent of making application-specific changes in
Configuration.java"
is really such a bad thing to overweight the advantage of having all changes in
precisely one class.
> 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.
