[
https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-10178:
-----------------------------------
Target Version/s: 3.0.0, 2.3.0
Hadoop Flags: Reviewed
Good catches Shanyu, and thank you for posting the summary of the behavior.
I'm +1 for the v7 patch.
[~tucu00], I'm planning to commit later today unless you object. Shanyu's
comment about the source message makes sense to me, but maybe we can change it
later in a separate patch if you have something else in mind. Thanks for
helping to review this patch.
> 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-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.1.5#6160)
