hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-6105) Provide a way to automatically handle backward compatibility of deprecated keys
Date Sat, 14 May 2011 05:14:48 GMT

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

Todd Lipcon commented on HADOOP-6105:
-------------------------------------

It seems there is a bit of a flaw in the way this JIRA was done. Could those who are still
watching this please take a look at HADOOP-7287? Thanks.

> Provide a way to automatically handle backward compatibility of deprecated keys
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-6105
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6105
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Hemanth Yamijala
>            Assignee: V.V.Chaitanya Krishna
>             Fix For: 0.21.0
>
>         Attachments: HADOOP-6105-1.patch, HADOOP-6105-10.patch, HADOOP-6105-2.patch,
HADOOP-6105-3.patch, HADOOP-6105-4.patch, HADOOP-6105-5.patch, HADOOP-6105-6.patch, HADOOP-6105-7.patch,
HADOOP-6105-8.patch, HADOOP-6105-9.patch, HADOOP-6105.patch, HADOOP-6105.patch
>
>
> There are cases when we have had to deprecate configuration keys. Use cases include,
changing the names of variables to better match intent, splitting a single parameter into
two - for maps, reduces etc.
> In such cases, we typically provide a backwards compatible option for the old keys. The
handling of such cases might typically be common enough to actually add support for it in
a generic fashion in the Configuration class. Some initial discussion around this started
in HADOOP-5919, but since the project split happened in between we decided to open this issue
to fix it in common.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message