[
https://issues.apache.org/jira/browse/HADOOP-11527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299105#comment-14299105
]
Chris Nauroth commented on HADOOP-11527:
----------------------------------------
[~aw], yes, these two patches will work nicely together. HADOOP-11485 can help
solve the problem of a distro automatically putting alternative file systems on
the classpath. (hadoop-tools stuff isn't on the classpath by default.)
HADOOP-11527 makes it so that presence of the file system's jar in the
classpath is completely sufficient for registering its existence to the rest of
the Hadoop code.
I've been interested in HADOOP-11485, and I have it in my review queue. I'll
try to take a look next week.
> 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)
