hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1932) Add utility method to initialize HDFS default configurations
Date Mon, 16 May 2011 05:31:47 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033881#comment-13033881

Eli Collins commented on HDFS-1932:

Thanks Jolly.  Do we need to call HdfsConfiguration#init in these n places to make sure it's
loaded? If so, is there 1 place that would suffice?  The latest patch looks good, I'm just
wondering if there's a better way to implement it.

In terms of testing does the test in HADOOP-7287 fail w/o this patch and succeed with it?

> Add utility method to initialize HDFS default configurations
> ------------------------------------------------------------
>                 Key: HDFS-1932
>                 URL: https://issues.apache.org/jira/browse/HDFS-1932
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Jolly Chen
>            Priority: Critical
>              Labels: newbie
>         Attachments: hdfs-1932-2.txt, hdfs-1932.txt
> Currently we have code blocks like the following in lots of places:
> {code}
>   static{
>     Configuration.addDefaultResource("hdfs-default.xml");
>     Configuration.addDefaultResource("hdfs-site.xml");
>   }
> {code}
> This is dangerous since, if we don't remember to also classload HdfsConfiguration, the
config key deprecations won't work. We should add a method like HdfsConfiguration.init() which
would load the default resources as well as ensure that deprecation gets initialized properly.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message