You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "shanyu zhao (JIRA)" <ji...@apache.org> on 2013/12/22 03:00:50 UTC

[jira] [Updated] (HADOOP-10178) Configuration deprecation always emit "deprecated" warnings when a new key is used

     [ https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

shanyu zhao updated HADOOP-10178:
---------------------------------

    Attachment: HADOOP-10178.patch

Patch attached.

The root cause of this problem is that the fix for HADOOP-8167 put deprecated keys (even if you're adding a new key) into the variable "properties", this will cause deprecated warning when handleDeprecation() is called. Note that handleDeprecation() has to be called otherwise it won't catch deprecated keys in configuration files.

This fix basically reversed HADOOP-8167 and fixed HADOOP-8167 in a different way: modified iterator() implementation to include all deprecated keys. 

> 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.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)