[
https://issues.apache.org/jira/browse/HADOOP-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727460#action_12727460
]
Hemanth Yamijala commented on HADOOP-6105:
------------------------------------------
Philip, this seems a very ambitious change to the Configuration framework.
Before I can comment further, I would like to take a look at the exact JIRA
where this is being discussed. Though I could find out a couple of JIRAs that
seem related, none had all the points that you've mentioned here. Can you point
me to such a jira, if it exists ?
If not, I think it is important to open a new JIRA to discuss these points.
That way it will find a better audience and we can discuss better. Please let
me know about this.
> 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
>
> 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.
