[
https://issues.apache.org/jira/browse/HDFS-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Bokor resolved HDFS-2585.
--------------------------------
Resolution: Duplicate
> dfs.https.port is a bit confusing
> ---------------------------------
>
> Key: HDFS-2585
> URL: https://issues.apache.org/jira/browse/HDFS-2585
> Project: Hadoop HDFS
> Issue Type: Improvement
> Affects Versions: 0.23.0
> Reporter: Joe Crobak
> Priority: Trivial
>
> First off, dfs.https.address was renamed to dfs.namenode.https-address, so it
> would make sense to deprecate dfs.https.port and rename it to
> dfs.namenode.https-address for consistency. Yet, it also appears that
> dfs.namenode.https-address includes the port number, so it's unclear to me
> why a separate port property exists.
> In addition, in DFSConfigKeys.java, both DFS_NAMENODE_HTTPS_PORT_KEY and
> DFS_HTTPS_PORT_KEY use this string as a key.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
