[
https://issues.apache.org/jira/browse/HADOOP-15142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318868#comment-16318868
]
Steve Loughran commented on HADOOP-15142:
-----------------------------------------
1. I think where were going with ftp/sftp is retire the current set and switch
to the one proposed HADOOP-14444. That's lacking in reviews by people who have
promised to test it (myself included!), and, because its going against
different FTP systems, needs lots of cross system testing
Given you are using ftp, why not play with that.
Regarding the patch, the FS is registered in core-default.xml as fs.ftp.impl,
and I think it should stay that way, given the history of problems we've had
with the dynamic registration and classpaths.
I don't see anything related to sftp in core-default. It needs a reference in
the file, which is something we can backport to those branches which won't get
the new FTP client. Would you like just to do that, rather than the dynamic
bit? The scheme bit you could leave in for consistency, even though it won't
get used
> Register FTP and SFTP as FS services
> ------------------------------------
>
> Key: HADOOP-15142
> URL: https://issues.apache.org/jira/browse/HADOOP-15142
> Project: Hadoop Common
> Issue Type: New Feature
> Components: common
> Affects Versions: 3.0.0
> Reporter: Mario Molina
> Priority: Minor
> Fix For: 3.0.1
>
> Attachments: HADOOP-15142.001.patch
>
>
> SFTPFileSystem and FTPFileSystem are not registered as a FS services.
> When calling the 'get' or 'newInstance' methods of the FileSystem class, the
> FS instance cannot be created due to the schema is not registered as a
> service FS.
> Also, the SFTPFileSystem class doesn't have the getScheme method implemented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
