[
https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-10178:
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
3.0.0
Status: Resolved (was: Patch Available)
I committed this to trunk, branch-2 and branch-2.3. Shanyu, thank you for the
patch. Alejandro, thank you for help with code review.
> 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.1.5#6160)
