[
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-8.patch
Changes introduced in the new patch:
* made {{hadoop.conf.extra.classes}} as a static final string.
* introduced a testcase which ensures that there are no side-effects of
reloadConfiguration on deprecations and get() of the new and old keys.
* in order to ensure that deprecatedKeyMap data structure is not modified after
loading all the resources for the first time, it is changed to unmodifiable
after getting populated.
* modified set(String, String) in order to ensure that even if a set() is
called before the first get(), the deprecation information is populated and
keys are set accordingly.
* wrapped the methods populateDeprecationMapping() and processDeprecatedKeys()
with new method processDeprecation() for better understanding of code.
> 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-7.patch, HADOOP-6105-8.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.
