[
https://issues.apache.org/jira/browse/HADOOP-8967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14513398#comment-14513398
]
Hadoop QA commented on HADOOP-8967:
-----------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12728282/HADOOP-8967.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 1a2459b |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6189/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
> Assignee: Robert Joseph Evans
> Priority: Minor
> 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)
