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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/01 07:22:04 UTC

[jira] [Updated] (HADOOP-9854) Configuration.set() may be called before all the deprecated keys are registered, causing inconsistent state

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

Allen Wittenauer updated HADOOP-9854:
-------------------------------------
    Priority: Major  (was: Blocker)

> Configuration.set() may be called before all the deprecated keys are registered, causing inconsistent state
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9854
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9854
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 2.0.5-alpha
>            Reporter: Sangjin Lee
>
> Currently deprecated keys are registered at various times. Some are registered  when the Configuration class itself is initialized, but the vast majority are registered when the JobConf class is initialized.
> Therefore, it is entirely possible (and does happen) that Configuration.set() is called for a key before its deprecation mapping is registered, thus leaving the internal state of Configuration in an inconsistent state.
> We actually had this problem occur in real life, causing the set value not to be recognized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)