[
https://issues.apache.org/jira/browse/HADOOP-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15081298#comment-15081298
]
Hadoop QA commented on HADOOP-8967:
-----------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color}
| {color:red} HADOOP-8967 does not apply to trunk. Rebase required? Wrong
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12728282/HADOOP-8967.patch |
| JIRA Issue | HADOOP-8967 |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/8336/console |
This message was automatically generated.
> 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)
