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 "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/01/30 20:19:34 UTC

[jira] [Commented] (HADOOP-11527) Support ServiceLoader mechanism for finding subclasses of AbstractFileSystem.

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

Allen Wittenauer commented on HADOOP-11527:
-------------------------------------------

Just out of curiosity, does HADOOP-11485 help here by allowing AbstractFileSystems to include a plug in that would could inject bits into the command line and in the CLASSPATH without the user doing anything?

> Support ServiceLoader mechanism for finding subclasses of AbstractFileSystem.
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-11527
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11527
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>            Reporter: Chris Nauroth
>
> Currently, Hadoop code can discover custom implementations of {{FileSystem}} via either configuration mapping the scheme to the class name or the Java {{ServiceLoader}} mechanism.  However, for implementations of {{AbstractFileSystem}}, only configuration is supported and not the {{ServiceLoader}} mechanism.  Because of this, we must either specify the classes in core-default.xml (which is somewhat unusual because the class is likely to be in a hadoop-tools module instead of hadoop-common) or ask users to set it in core-site.xml at deployment time.  This issue proposes to implement the {{ServiceLoader}} mechanism for {{AbstractFileSystem}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)