[
https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485305#comment-13485305
]
Alejandro Abdelnur commented on HADOOP-7549:
--------------------------------------------
Jane,
If you are unjaring/rejaring Hadoop JARs when using Hadoop from a JVM started
from C++ then that could be the issue. JDK ServiceLoader uses the same file
name in multiple JARs to pick up all services. If you unjar/rejar the JARs, you
are looking all but one of those files.
You could try using the old mechanism for registering filesystems in the hadoop
configuration files 'fs.<SCHEME>.impl=<CLASS>.
> Use JDK ServiceLoader mechanism to find FileSystem implementations
> ------------------------------------------------------------------
>
> Key: HADOOP-7549
> URL: https://issues.apache.org/jira/browse/HADOOP-7549
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Affects Versions: 0.23.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 2.0.0-alpha
>
> Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch,
> HADOOP-7549v3.patch
>
>
> Currently configuring FileSystem implementations must be done by declaring
> the FileSystem class in the Hadoop configuration files (core-default.xml,
> ...).
> Using JDK ServiceLoader mechanism this configuration step can be avoided.
> Adding the JAR file with the additional FileSystem implementation would
> suffice.
> This is similar to what is being proposed for compression codecs
> (HADOOP-7350).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
