[ https://issues.apache.org/jira/browse/HADOOP-6105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733919#action_12733919 ]
Philip Zeyliger commented on HADOOP-6105: ----------------------------------------- I think you have to think about how Hadoop's notion of a "final" flag interacts with this, too. If a system administrator has set either A or B to be final, then that value must override any user-submitted value, regardless of which was set first. > 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.