[
https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866087#comment-13866087
]
Alejandro Abdelnur commented on HADOOP-10178:
---------------------------------------------
+1. I've looked at the patch and played a bit with it (modifying the testcase)
and it seems to work as advertised.
Only NIT (not introduced by the patch but we can fix in the context of the
patch) is the <source> message:
{code}
<property><name>BB</name><value>xx</value><source>because CC is
deprecated</source></property>
{code}
Can we change it to something like *Using 'BB' because 'CC' is deprecated* ?
> 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
> Attachments: HADOOP-10178-v2.patch, HADOOP-10178-v3.patch,
> HADOOP-10178-v4.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.1.5#6160)
