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 "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2016/01/04 16:58:39 UTC

[jira] [Updated] (HADOOP-8967) Reported source for config property can be misleading

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

Robert Joseph Evans updated HADOOP-8967:
----------------------------------------
    Assignee:     (was: Robert Joseph Evans)

> Reported source for config property can be misleading
> -----------------------------------------------------
>
>                 Key: HADOOP-8967
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8967
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.23.3
>            Reporter: Jason Lowe
>            Priority: Minor
>              Labels: BB2015-05-TBR
>         Attachments: HADOOP-8967.patch, HADOOP-8967.txt
>
>
> Configuration.set tries to track the source of a property being set, but it mistakenly reports properties as being deprecated when they are not.  This is misleading and confusing for users examining a job's configuration.
> For example, run a sleep job and check the job configuration on the job UI.  The source for the "mapreduce.job.maps" property will be reported as "job.xml ⬅ because mapreduce.job.maps is deprecated".  This leads users to think mapreduce.job.maps is now a deprecated property and wonder what other property they should use instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)