[
https://issues.apache.org/jira/browse/HADOOP-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752445#action_12752445
]
Hudson commented on HADOOP-6105:
--------------------------------
Integrated in Hadoop-Common-trunk #89 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/89/])
. Adds support for automatically handling deprecation of configuration
keys. Contributed by V.V.Chaitanya Krishna.
> 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.
-
You can reply to this email to add a comment to the issue online.
