hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13399) deprecate the Configuration classloader
Date Thu, 21 Jul 2016 22:02:20 GMT

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

Sean Busbey commented on HADOOP-13399:

Deprecate in branch-2 and remove in one of the 3.0 alphas?

> deprecate the Configuration classloader
> ---------------------------------------
>                 Key: HADOOP-13399
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13399
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: util
>            Reporter: Sangjin Lee
>            Assignee: Sangjin Lee
>            Priority: Critical
> Today, anyone can simply call {{Configuration.setClassLoader()}} to set the configuration
classloader to any arbitrary classloader. This classloader is then used to get a class or
a resource through {{Configuration}} ({{getClass()}} and {{getResource()}}).
> In essence, the {{Configuration}} classloader is effectively a globally shared classloader
without contract. This is one step worse than TCCL in that regard.
> I propose to remove/deprecate {{setClassLoader()}} and {{getClassLoader()}} and simply
use TCCL (and then the classloader that loaded the {{Configuration}} class) to load classes
and resources.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message