Return-Path: X-Original-To: apmail-hadoop-common-dev-archive@www.apache.org Delivered-To: apmail-hadoop-common-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E20B5C906 for ; Wed, 23 May 2012 07:37:45 +0000 (UTC) Received: (qmail 75358 invoked by uid 500); 23 May 2012 07:37:44 -0000 Delivered-To: apmail-hadoop-common-dev-archive@hadoop.apache.org Received: (qmail 75281 invoked by uid 500); 23 May 2012 07:37:43 -0000 Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-dev@hadoop.apache.org Delivered-To: mailing list common-dev@hadoop.apache.org Received: (qmail 75229 invoked by uid 99); 23 May 2012 07:37:41 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2012 07:37:41 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id C17BB14281C for ; Wed, 23 May 2012 07:37:41 +0000 (UTC) Date: Wed, 23 May 2012 07:37:41 +0000 (UTC) From: "Subroto Sanyal (JIRA)" To: common-dev@hadoop.apache.org Message-ID: <602584244.10822.1337758661794.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HADOOP-8426) API to get info for deprecated key MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Subroto Sanyal created HADOOP-8426: -------------------------------------- Summary: API to get info for deprecated key Key: HADOOP-8426 URL: https://issues.apache.org/jira/browse/HADOOP-8426 Project: Hadoop Common Issue Type: Bug Components: conf Affects Versions: 0.23.1 Reporter: Subroto Sanyal The current version of Hadoop deprecates many keys but, takes care of adding the new keys to the configuration accordingly. For the end user only logs are there which indicates the key is deprecated and the message also suggests the new key to be used. I was thinking; there should be an API/Utility which could probably provide the new key information when called with old key. Using this API the user can judge in runtime to use the old key or new key. Currently the Configuration provides an API only to check whether a key is deprecated or not but, doesn't provides a way to get the corresponding new 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