[ https://issues.apache.org/jira/browse/HADOOP-7287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13037517#comment-13037517 ]
Hadoop QA commented on HADOOP-7287: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12479976/hadoop-7287-trunk.2.patch against trunk revision 1125221. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 system test framework. The patch passed system test framework compile. Test results: https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/496//testReport/ Findbugs warnings: https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/496//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/496//console This message is automatically generated. > Configuration deprecation mechanism doesn't work properly for > GenericOptionsParser/Tools > ---------------------------------------------------------------------------------------- > > Key: HADOOP-7287 > URL: https://issues.apache.org/jira/browse/HADOOP-7287 > Project: Hadoop Common > Issue Type: Bug > Components: conf > Affects Versions: 0.22.0, 0.23.0 > Reporter: Todd Lipcon > Assignee: Aaron T. Myers > Priority: Blocker > Fix For: 0.22.0, 0.23.0 > > Attachments: hadoop-7287-still-broken.txt, hadoop-7287-testcase.txt, > hadoop-7287-trunk.0.patch, hadoop-7287-trunk.1.patch, > hadoop-7287-trunk.2.patch > > > For example, you can't use -D options on the "hadoop fs" command line in > order to specify the deprecated names of configuration options. The issue is > that the ordering is: > - JVM starts > - GenericOptionsParser creates a Configuration object and calls set() for > each of the options specified on command line > - DistributedFileSystem or other class eventually instantiates > HdfsConfiguration which adds the deprecations > - Some class calls conf.get("new key") and sees the default instead of the > version set on the command line -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira