Return-Path: Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: (qmail 16401 invoked from network); 6 Aug 2009 18:02:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Aug 2009 18:02:31 -0000 Received: (qmail 57135 invoked by uid 500); 6 Aug 2009 18:02:39 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 57046 invoked by uid 500); 6 Aug 2009 18:02:39 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 57036 invoked by uid 99); 6 Aug 2009 18:02:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 18:02:39 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2009 18:02:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D74A6234C04B for ; Thu, 6 Aug 2009 11:02:14 -0700 (PDT) Message-ID: <971019825.1249581734880.JavaMail.jira@brutus> Date: Thu, 6 Aug 2009 11:02:14 -0700 (PDT) From: "Jitendra Nath Pandey (JIRA)" To: hdfs-dev@hadoop.apache.org Subject: [jira] Created: (HDFS-531) Renaming of configuration keys MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Renaming of configuration keys ------------------------------ Key: HDFS-531 URL: https://issues.apache.org/jira/browse/HDFS-531 Project: Hadoop HDFS Issue Type: Improvement Reporter: Jitendra Nath Pandey Assignee: Jitendra Nath Pandey Fix For: 0.21.0 Keys in configuration files should be standardized so that key names reflect the components they are used in. For example: dfs.backup.address should be renamed to dfs.namenode.backup.address dfs.data.dir should be renamed to dfs.datanode.backup.address This change will impact both hdfs and common sources. Following convention is proposed: 1. Any key related hdfs should begin with 'dfs'. 2. Any key related to namenode, datanode or client should begin with dfs.namenode, dfs.datanode or dfs.client respectively. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.