[
https://issues.apache.org/jira/browse/HDFS-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044254#comment-14044254
]
Aaron T. Myers commented on HDFS-5321:
--------------------------------------
I very much disagree with the notion of "private configurations." To my
knowledge we've never made such a distinction, and if we have been then it
certainly should have been called out more explicitly for each individual
setting than the mere absence of them from {{hdfs-default.xml}}.
bq. Since HDFS maintains no compatibility guarantees for private
configurations, it should be okay to include this in minor releases.
Where are you concluding this from? Our compatibility guide makes no mention of
it, or the concept of "private configurations" at all:
http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-common/Compatibility.html
I think we should seriously consider reverting this change. The stated benefits
seem quite minor, these conf settings have never been deprecated properly using
DeprecationDelta (meaning users have never seen printed warnings about the
deprecation), and this is a clearly incompatible change that has the potential
to break existing applications as-written.
> Clean up the HTTP-related configuration in HDFS
> -----------------------------------------------
>
> Key: HDFS-5321
> URL: https://issues.apache.org/jira/browse/HDFS-5321
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Fix For: 2.4.0
>
> Attachments: HDFS-5321.000.patch, HDFS-5321.001.patch
>
>
> Currently there are multiple configuration keys that control the ports that
> the NameNode and DataNode listen to, and the default ports that the
> hftp/webhdfs clients are connecting to.
> Below is a quick summary of these configuration:
> || Keys || Description ||
> | dfs.namenode.http-address | The address that the namenode http server binds
> to |
> | dfs.namenode.https-address | The address that the namenode https server
> binds to |
> | dfs.http.port | The default port that the hftp/webhdfs client use to
> connect to the remote server|
> | dfs.https.port | The default port that the hsftp client use to connect to
> the remote server|
> I propose to deprecate dfs.http.port and dfs.https.port to avoid potential
> confusions (e.g., HDFS-5316). Note that this removes no functionality, since
> the users can specify ports in hftp / webhdfs URLs when they need to connect
> to HDFS servers with non-default ports.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
