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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.5-alpha
• Component/s: conf, documentation
• Assignee: Unassigned
• Reporter: Sangjin Lee
• Created: 09/Aug/13 00:26
• Updated: 01/Mar/15 06:22

Description

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.