hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9735) Deprecated configuration property can overwrite non-deprecated property
Date Tue, 16 Jul 2013 14:16:49 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-9735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709797#comment-13709797
] 

Jason Lowe commented on HADOOP-9735:
------------------------------------

Having deprecated properties overwrite non-deprecated properties is intentional -- it's how
we support deprecated properties.  The converse is also true -- setting a property will also
set all the deprecated forms of that property.  Essentially the deprecated properties are
aliases with warnings attached when used.  Failure to set the "true" property when a deprecated
property is set will break support of deprecated properties.

bq. In the meanwhile, Configuration#getPropertySources may return wrong source information
for a deprecated property.

This is a known issue, tracked by HADOOP-8967.
                
> 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

Mime
View raw message