[HADOOP-8167] Configuration deprecation logic breaks backwards compatibility

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.3, 0.24.0
• Fix Version/s: 0.23.3, 2.0.2-alpha
• Component/s: conf
• Hadoop Flags: Reviewed
• Assignee: Alejandro Abdelnur
• Reporter: Alejandro Abdelnur
• Created: 13/Mar/12 16:32
• Updated: 07/Jan/14 19:27
• Resolved: 14/Mar/12 17:08

Description

The deprecated Configuration logic works as follows:

For a dK deprecated key in favor of nK:

• on set(dK, V), it stores (nK,V)
• on get(dK) it does a reverseLookup of dK to nK and looks for get(nK)

While this works fine for single set/get operations, the iterator() method that returns an iterator of all config key/values, returns only the new keys.

This breaks applications that did a set(dK, V) and expect, when iterating over the configuration to find (dK, V).

Issue Links

• breaks: HADOOP-8172 Configuration no longer sets all keys in a deprecated key list.
• is depended upon by: OOZIE-761 Fixes in CoordELFunctions and testcases for Hadoop 0.23
• is related to: HADOOP-10178 Configuration deprecation always emit "deprecated" warnings when a new key is used