Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Mon, 3 Mar 2014 15:55:21 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12634553.1362025046882.3316.1393862121907@arcas>
In-Reply-To: <JIRA.12634553.1362025046882@arcas>
References: <JIRA.12634553.1362025046882@arcas>
Subject: [jira] [Resolved] (HADOOP-9344) Configuration.writeXml can warn
 about deprecated properties user did not set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jason Lowe resolved HADOOP-9344.
--------------------------------

    Resolution: Duplicate

Looks like this was fixed by HADOOP-10178.

> Configuration.writeXml can warn about deprecated properties user did not set
> ----------------------------------------------------------------------------
>
>                 Key: HADOOP-9344
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9344
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 2.0.3-alpha, 0.23.5
>            Reporter: Jason Lowe
>            Assignee: Rushabh S Shah
>
> When the configuration is serialized it can emit warnings about deprecated properties that the user did not specify.  Converting the config to XML causes all the properties in the config to be processed for deprecation, and after HADOOP-8167 setting a proper config property also causes the deprecated forms to be set.  Processing all the keys in the config for deprecation therefore can trigger warnings for keys that were never specified by the user, leaving users confused as to how their code could be triggering these warnings.


--
This message was sent by Atlassian JIRA
(v6.2#6252)