Details
-
Improvement
-
Status: Resolved
-
Trivial
-
Resolution: Duplicate
-
0.23.0
-
None
-
None
-
None
Description
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.