You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2013/08/09 02:27:48 UTC

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

Sangjin Lee created HADOOP-9854:
-----------------------------------

             Summary: 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 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