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 "Alejandro Abdelnur (Updated) (JIRA)" <ji...@apache.org> on 2012/03/13 19:32:38 UTC
[jira] [Updated] (HADOOP-8167) Configuration deprecation logic
breaks backwards compatibility
[ https://issues.apache.org/jira/browse/HADOOP-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alejandro Abdelnur updated HADOOP-8167:
---------------------------------------
Attachment: HADOOP-8167.patch
Going for option #2, seems the least invasive one. taking care of unset as well. added testcases
> Configuration deprecation logic breaks backwards compatibility
> --------------------------------------------------------------
>
> Key: HADOOP-8167
> URL: https://issues.apache.org/jira/browse/HADOOP-8167
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.24.0, 0.23.3
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Blocker
> Fix For: 0.23.3
>
> Attachments: HADOOP-8167.patch
>
>
> The deprecated Configuration logic works as follows:
> For a dK deprecated key in favor of nK:
> * on set(dK, V), it stores (nK,V)
> * on get(dK) it does a reverseLookup of dK to nK and looks for get(nK)
> While this works fine for single set/get operations, the iterator() method that returns an iterator of all config key/values, returns only the new keys.
> This breaks applications that did a set(dK, V) and expect, when iterating over the configuration to find (dK, V).
--
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