Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 19 Jul 2013 02:04:48 +0000 (UTC)
From: "Kousuke Saruta (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12658438.1374114530446.78648.1374199488714@arcas>
In-Reply-To: <JIRA.12658438.1374114530446@arcas>
References: <JIRA.12658438.1374114530446@arcas>
Subject: [jira] [Updated] (HDFS-5007) the property key "dfs.http.port" and
 "dfs.https.port" are hard corded
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kousuke Saruta updated HDFS-5007:
---------------------------------

    Status: Open  (was: Patch Available)
    
> 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
>            Assignee: 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