[
https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909412#comment-13909412
]
Dave Winters commented on HADOOP-10178:
---------------------------------------
I worked with this patch for a while trying to get it to apply to the straight
pull from Apache.
Unfortunately out of the 6 hunks only 1 was successful.
I went and looked at the HDP sources and did a 'diff -ru' and my sources and
noticed some issues.
What I ended up doing was pulling and using their Configuration.java code and
then building.
It eliminated the depreciation messages and the compile time errors for missing
'deprecation' variable.
Now this could be "driver error" on my part. So this comment is just a heads up
that this patch may not be as plug and play in the wild as by parties that are
constantly contributing and commiting.
Cheers - Bunnyworks
> 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)
