hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kousuke Saruta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and "dfs.https.port" are hard corded
Date Thu, 18 Jul 2013 09:18:51 GMT

     [ https://issues.apache.org/jira/browse/HDFS-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kousuke Saruta updated HDFS-5007:

    Attachment: HDFS-5007.patch

I explored unused/duplicated fields in DFSConfigKeys and I found only DFS_HTTPS_PORT is unused
and there are no duplicated fields except for dfs.https.port.
> the property key "dfs.http.port" and "dfs.https.port" are hard corded
> ---------------------------------------------------------------------
>                 Key: HDFS-5007
>                 URL: https://issues.apache.org/jira/browse/HDFS-5007
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Kousuke Saruta
>             Fix For: 3.0.0
>         Attachments: HDFS-5007.patch, HDFS-5007.patch
> In "TestHftpFileSystem.java" and "NameNodeHttpServer.java" , the two property key "dfs.http.port"
and "dfs.https.port" are hard corded.
> Now, the constant values "DFS_NAMENODE_HTTP_PORT_KEY" and "DFS_NAMENODE_HTTPS_KEY" in
DFSConfigKeys are available so I think we should replace those for maintainability. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message