hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-6252) Provide method to determine if a deprecated key was set in the config file
Date Fri, 11 Sep 2009 00:09:57 GMT

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

Suresh Srinivas updated HADOOP-6252:
------------------------------------

    Fix Version/s: 0.21.0

> 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
>             Fix For: 0.21.0
>
>         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.


Mime
View raw message