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 "Jakob Homan (JIRA)" <ji...@apache.org> on 2009/09/11 00:19:57 UTC

[jira] Updated: (HADOOP-6252) Provide method to determine if a deprecated key was set in the config file

     [ https://issues.apache.org/jira/browse/HADOOP-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Homan updated HADOOP-6252:
--------------------------------

    Attachment: HADOOP-6252.patch

Patch:
   * Implements new method to see if deprecated key had been used in config file
   * Provides test for this functionality
   * Removes unnecessary import


> Provide method to determine if a deprecated key was set in the config file
> --------------------------------------------------------------------------
>
>                 Key: HADOOP-6252
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6252
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: conf
>    Affects Versions: 0.21.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>         Attachments: HADOOP-6252.patch
>
>
> HADOOP-6105 provided a method to deprecate config keys and transparently refer to the new key. However, it didn't provide a method to see if the deprecated key had been used in the config file.  This is useful when, if the deprecated key had been used, its value needs to be converted before use, for instance when we changed the umask format.  A method like "boolean wasDeprecatedKeySet()" would be great.  Patch shortly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.