You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2013/07/16 09:26:49 UTC
[jira] [Updated] (HADOOP-9735) Deprecated configuration property
can overwrite non-deprecated property
[ https://issues.apache.org/jira/browse/HADOOP-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jing Zhao updated HADOOP-9735:
------------------------------
Attachment: deprecated-conf.test.patch
Unit tests to demo the two issues in the description.
> Deprecated configuration property can overwrite non-deprecated property
> -----------------------------------------------------------------------
>
> Key: HADOOP-9735
> URL: https://issues.apache.org/jira/browse/HADOOP-9735
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.1.0-beta
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Priority: Minor
> Attachments: deprecated-conf.test.patch
>
>
> For the current Configuration implementation, if a conf file contains definitions for both a non-deprecated property and its corresponding deprecated property (e.g., fs.defaultFS and fs.default.name), the latter will overwrite the previous one. In the fs.defaultFS example, this may cause client failover not work. It may be better to keep the non-deprecated property's value unchanged.
> In the meanwhile, Configuration#getPropertySources may return wrong source information for a deprecated property. E.g., after setting fs.defaultFS, Configuration#getPropertySources("fs.default.name") will return "because fs.defaultFS is deprecated".
--
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