hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Crobak (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-2585) dfs.https.port is a bit confusing
Date Tue, 22 Nov 2011 17:20:40 GMT
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message