[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555732#action_12555732
]
Doug Cutting commented on HADOOP-2404:
--------------------------------------
> Doug, you are trying to kill two birds with this one, provide compatibility
> and clean up the configuration mess.
No, I'm trying to provide compatibility without creating a new mess, by using
this as an opportunity to decrease the mess by doing this the way it should
have been done in the original patch. The original patch should have been
rejected because it was not back-compatible. We're not yet under a code
freeze, so we're under no pressure to create a minimally invasive patch. We
should instead be trying to write exemplary code. It is not a good practice to
modify the user's configuration instance. It is a good practice to handle
back-compatibility for configuration options by adding accessor methods and
using those wherever the option is accessed. That's what should have been done
in the original patch and that's what we should do now.
We don't need a new public class called ConfigurationConverter in the util
package. That's a step in the wrong direction. Back-compatibility should be
localized whenever possible, not thrown into a big pot.
> 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.
