Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 13 Mar 2012 21:24:39 +0000 (UTC)
From: "Alejandro Abdelnur (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <428946566.9607.1331673879734.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <378830738.8369.1331656362048.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8167) Configuration deprecation logic
 breaks backwards compatibility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13228726#comment-13228726 ] 

Alejandro Abdelnur commented on HADOOP-8167:
--------------------------------------------

The failed test 'TestViewFS' seems unrelated
                
> 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