Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for WASB(s) (Azure Blobs) scheme. #58

Open
nperumal opened this issue Mar 21, 2019 · 1 comment
Open

Add support for WASB(s) (Azure Blobs) scheme. #58

nperumal opened this issue Mar 21, 2019 · 1 comment

Comments

@nperumal
Copy link

It would be nice to have support for WASB(s) scheme.
PierreAlexMaury pushed a commit to PierreAlexMaury/spark-sftp that referenced this issue Dec 9, 2019
fix egen#58 Remove the hard dependency to HDFS
a0b34a7 
Modify the condition to evaluate the case we are NOT on local FS. Doing this way it's wasb(s) or s3 compatible if the cluster is based on this kind of distributed filesystem
PierreAlexMaury pushed a commit to PierreAlexMaury/spark-sftp that referenced this issue Dec 9, 2019
fix egen#58 Remove the hard dependency to HDFS
5f893e5 
Modify the condition to evaluate the case we are NOT on local FS. Doing this way it's wasb(s) or s3 compatible if the cluster is based on this kind of distributed filesystem
@FurcyPin
Copy link

We identified that the problem is that code currently checks if the FileSystem.getScheme() is "hdfs" to know if it is running in local or distributed mode.

However, when running on cloud distributions (AWS EMR, Azure HDInsight, Google DataProc, and probably Databricks too) the scheme is not "hdfs" (but instead "s3", "wasbs", "gs", etc.).

The above pull requests fixes that. (We only tested it on WASB(s) but we believe it should fix the issue for other clouds as well).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nperumal @FurcyPin