hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.V.Chaitanya Krishna (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6105) Provide a way to automatically handle backward compatibility of deprecated keys
Date Wed, 02 Sep 2009 18:04:32 GMT

     [ 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-7.patch

* Uploading the patch with the above suggestions implemented. A new testcase {{TestConfigurationDeprecation}}
is coded for testing of the deprecation functionality. 
* As mentioned in the above comments, reloadConfiguration() will not flush the deprecated
key mappings and it will not trigger re-initialization of any of the classes that are once
initialized due to the presence of its class name in the value of property _hadoop.conf.extra.classes_
.
* The value of _hadoop.conf.extra.classes_ is currently set to the class name of JobConf in
mapreduce. It can be added with the class name(s) in hdfs which  extend Configuration and
whose static block has deprecations related to hdfs.

> 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.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.


Mime
View raw message