[HADOOP-8172] Configuration no longer sets all keys in a deprecated key list.

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.23.3, 0.24.0
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: conf
• Target Version/s: 0.23.3
• Assignee: Anupam Seth
• Reporter: Robert Joseph Evans
• Created: 15/Mar/12 15:07
• Updated: 07/Sep/12 21:01
• Resolved: 01/May/12 21:47

Description

I did not look at the patch for HADOOP-8167 previously, but I did in response to a recent test failure. The patch appears to have changed the following code (I am just paraphrasing the code)

if(!deprecated(key)) {
  set(key, value);
} else {
  for(String newKey: depricatedKeyMap.get(key)) {
    set(newKey, value);
  }
}

to be

set(key, value);
if(depricatedKeyMap.contains(key)) {
   set(deprecatedKeyMap.get(key)[0], value);
} else if(reverseKeyMap.contains(key)) {
   set(reverseKeyMap.get(key), value);
}

If a key is deprecated and is mapped to more then one new key value only the first one in the list will be set, where as previously all of them would be set.

Issue Links

• is broken by: HADOOP-8167 Configuration deprecation logic breaks backwards compatibility