hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-10178) Configuration deprecation always emit "deprecated" warnings when a new key is used
Date Fri, 01 Aug 2014 19:31:39 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-10178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14082803#comment-14082803
] 

Jason Lowe commented on HADOOP-10178:
-------------------------------------

I think this broke deprecated properties for streaming jobs.  See MAPREDUCE-6022.

> 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.2#6252)

Mime
View raw message