Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6C63DF94E for ; Wed, 17 Jul 2013 05:52:53 +0000 (UTC) Received: (qmail 45765 invoked by uid 500); 17 Jul 2013 05:52:52 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 45550 invoked by uid 500); 17 Jul 2013 05:52:52 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 45519 invoked by uid 99); 17 Jul 2013 05:52:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jul 2013 05:52:50 +0000 Date: Wed, 17 Jul 2013 05:52:50 +0000 (UTC) From: "Kousuke Saruta (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-5002) DFS_HTTPS_PORT_KEY is no longer refered MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kousuke Saruta updated HDFS-5002: --------------------------------- Attachment: HDFS-5002.patch I have attached a patch for trunk. > DFS_HTTPS_PORT_KEY is no longer refered > --------------------------------------- > > Key: HDFS-5002 > URL: https://issues.apache.org/jira/browse/HDFS-5002 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 3.0.0 > Reporter: Kousuke Saruta > Priority: Minor > Fix For: 3.0.0 > > Attachments: HDFS-5002.patch > > > In DFSConfigKeys of trunk, there is DFS_HTTPS_PORT_KEY field although it is no longer refered by any code. -- 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