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

XML

Word

Printable

JSON

Details

Type: Bug
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: 2.2.0
Fix Version/s: 2.3.0
Component/s: conf
Labels:
None

Target Version/s:

2.3.0
Hadoop Flags:

Reviewed

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

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

HADOOP-10178.patch
22/Dec/13 01:59
7 kB
shanyu zhao
HADOOP-10178-v2.patch
25/Dec/13 01:41
8 kB
shanyu zhao
HADOOP-10178-v3.patch
27/Dec/13 04:35
8 kB
shanyu zhao
HADOOP-10178-v4.patch
08/Jan/14 04:45
8 kB
shanyu zhao
HADOOP-10178-v5.patch
10/Jan/14 01:02
9 kB
shanyu zhao
HADOOP-10178-v6.patch
10/Jan/14 03:25
9 kB
shanyu zhao
HADOOP-10178-v7.patch
10/Jan/14 05:47
8 kB
shanyu zhao

Issue Links

breaks

MAPREDUCE-6022 map_input_file is missing from streaming job environment

Closed

is duplicated by

HADOOP-9344 Configuration.writeXml can warn about deprecated properties user did not set

Resolved

relates to

HADOOP-8167 Configuration deprecation logic breaks backwards compatibility

Closed

Activity

People

Assignee:: shanyu zhao

Reporter:: shanyu zhao

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 21/Dec/13 02:29

Updated:: 03/Sep/14 23:33

Resolved:: 10/Jan/14 20:20