[
https://issues.apache.org/jira/browse/HADOOP-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266119#comment-13266119
]
Hudson commented on HADOOP-8172:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #2168 (See
[https://builds.apache.org/job/Hadoop-Common-trunk-Commit/2168/])
HADOOP-8172. Configuration no longer sets all keys in a deprecated key
list. (Anupam Seth via bobby) (Revision 1332821)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1332821
Files :
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/conf/Configuration.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestConfigurationDeprecation.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/conf/TestDeprecatedKeys.java
> Configuration no longer sets all keys in a deprecated key list.
> ---------------------------------------------------------------
>
> Key: HADOOP-8172
> URL: https://issues.apache.org/jira/browse/HADOOP-8172
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.23.3, 0.24.0
> Reporter: Robert Joseph Evans
> Assignee: Anupam Seth
> Priority: Critical
> Attachments: HADOOP-8172-branch-2.patch, HADOOP-8172-branch-2.patch
>
>
> I did not look at the patch for HADOOP-8167 previously, but I did in response
> to a recent test failure. The patch appears to have changed the following
> code (I am just paraphrasing the code)
> {code}
> if(!deprecated(key)) {
> set(key, value);
> } else {
> for(String newKey: depricatedKeyMap.get(key)) {
> set(newKey, value);
> }
> }
> {code}
> to be
> {code}
> set(key, value);
> if(depricatedKeyMap.contains(key)) {
> set(deprecatedKeyMap.get(key)[0], value);
> } else if(reverseKeyMap.contains(key)) {
> set(reverseKeyMap.get(key), value);
> }
> {code}
> If a key is deprecated and is mapped to more then one new key value only the
> first one in the list will be set, where as previously all of them would be
> set.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
