[
https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082859#comment-14082859
]
Jason Lowe commented on HADOOP-10178:
-------------------------------------
I believe the streaming issue is caused by the assumption that if one doesn't
set a property by a deprecated name then nothing will break if the deprecated
names don't appear when iterating. Streaming breaks that assumption because
non-deprecated keys are used to setup the conf, but the conf is then iterated
to generate the environment variables for the streaming job. The streaming job
is trying to access the environment variables via the deprecated names, so it
doesn't have the luxury of the deprecated fixup being done by
Configuration.get(dK) to map to the new name.
> Configuration deprecation always emit "deprecated" warnings when a new key is
> used
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-10178
> URL: https://issues.apache.org/jira/browse/HADOOP-10178
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 2.2.0
> Reporter: shanyu zhao
> Assignee: shanyu zhao
> Fix For: 3.0.0, 2.3.0
>
> Attachments: HADOOP-10178-v2.patch, HADOOP-10178-v3.patch,
> HADOOP-10178-v4.patch, HADOOP-10178-v5.patch, HADOOP-10178-v6.patch,
> HADOOP-10178-v7.patch, HADOOP-10178.patch
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
