You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Mingliang Liu (JIRA)" <ji...@apache.org> on 2015/11/06 20:07:11 UTC
[jira] [Updated] (HDFS-9394) branch-2 hadoop-hdfs-client fails
during FileSystem ServiceLoader initialization, because HftpFileSystem is
missing.
[ https://issues.apache.org/jira/browse/HDFS-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu updated HDFS-9394:
--------------------------------
Attachment: HDFS-9394.000.branch-2.patch
Thank you [~cnauroth] for reporting this. As [~wheat9] said, when we separated the classes to {{hadoop-hdfs-client}}, we tried to address this in [HDFS-9166]. I think the original patch should work just fine, but it was probably not fully committed.
Hopefully the fix is simple. Let's see if the v0 patch works.
> branch-2 hadoop-hdfs-client fails during FileSystem ServiceLoader initialization, because HftpFileSystem is missing.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-9394
> URL: https://issues.apache.org/jira/browse/HDFS-9394
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: hdfs-client
> Reporter: Chris Nauroth
> Assignee: Mingliang Liu
> Priority: Critical
> Attachments: HDFS-9394.000.branch-2.patch
>
>
> On branch-2, hadoop-hdfs-client contains a {{FileSystem}} service descriptor that lists {{HftpFileSystem}} and {{HsftpFileSystem}}. These classes do not reside in hadoop-hdfs-client. Instead, they reside in hadoop-hdfs. If the application has hadoop-hdfs-client.jar on the classpath, but not hadoop-hdfs.jar, then this can cause a {{ServiceConfigurationError}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)