You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "V.V.Chaitanya Krishna (JIRA)" <ji...@apache.org> on 2009/08/03 07:17:15 UTC
[jira] Commented: (HADOOP-6105) Provide a way to automatically
handle backward compatibility of deprecated keys
[ https://issues.apache.org/jira/browse/HADOOP-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738191#action_12738191 ]
V.V.Chaitanya Krishna commented on HADOOP-6105:
-----------------------------------------------
Uploaded the patch with the above suggested modifications done.
> 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
> Attachments: HADOOP-6105-1.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.