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 Thu, 06 Aug 2009 06:49:14 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.patch

Some changes made in the new patch are:

- method to check if the key is deprecated.
- method to check if the key is previously loaded with the value of the corresponding deprecated
key.
- method to set value of deprecated key to the new keys ( when deprecated key occurs in xm
files).
- method to generate appropriate warning message that needs to be logged when deprecated key
is being considered.

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