[HADOOP-10178] Configuration deprecation always emit "deprecated" warnings when a new key is used

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.3.0
• Component/s: conf
• Target Version/s: 2.3.0
• Hadoop Flags: Reviewed
• Assignee: shanyu zhao
• Reporter: shanyu zhao
• Created: 21/Dec/13 02:29
• Updated: 03/Sep/14 23:33
• Resolved: 10/Jan/14 20:20

Description

Even if you use any new configuration properties, you still find "deprecated" warnings in your logs. E.g.:
13/12/14 01:00:51 INFO Configuration.deprecation: mapred.input.dir.recursive is deprecated. Instead, use mapreduce.input.fileinputformat.input.dir.recursive

Issue Links

• breaks: MAPREDUCE-6022 map_input_file is missing from streaming job environment
• is duplicated by: HADOOP-9344 Configuration.writeXml can warn about deprecated properties user did not set
• relates to: HADOOP-8167 Configuration deprecation logic breaks backwards compatibility