[jira] Updated: (HADOOP-6105) Provide a way to automatically handle backward compatibility of deprecated keys

["V.V.Chaitanya Krishna (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

V.V.Chaitanya Krishna updated HADOOP-6105:
------------------------------------------

    Attachment: HADOOP-6105-6.patch

The previous patch does not handle deprecations for mapreduce and hdfs. In order to support the deprecations in mapreduce and hdfs, a new key *hadoop.conf.extra.classes* is being added in core-site.xml. This key can have values as class names of classes from mapreduce and hdfs which extend Configuration and whose static blocks can have deprecations by using addDeprecation method. These classes will be loaded using reflection, thus ensuring that deprecations added in their static blocks are being considered.

Uploading a patch with the above changes made.

> 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
>         Attachments: HADOOP-6105-1.patch, HADOOP-6105-2.patch, HADOOP-6105-3.patch, HADOOP-6105-4.patch, HADOOP-6105-5.patch, HADOOP-6105-6.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.