srowen commented on a change in pull request #25737: [SPARK-29028][DOCS] Add 
links to IBM Cloud Object Storage connector in cloud-integration.md
URL: https://github.com/apache/spark/pull/25737#discussion_r322491989
 
 

 ##########
 File path: docs/cloud-integration.md
 ##########
 @@ -257,4 +257,5 @@ Here is the documentation on the standard connectors both 
from Apache and the cl
 * [Amazon EMR File System 
(EMRFS)](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-fs.html). 
From Amazon
 * [Google Cloud Storage Connector for Spark and 
Hadoop](https://cloud.google.com/hadoop/google-cloud-storage-connector). From 
Google
 * [The Azure Blob Filesystem driver 
(ABFS)](https://docs.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-abfs-driver)
+* IBM Cloud Object Storage connector for Apache Spark : 
[Stocator,](https://github.com/CODAIT/stocator) [IBM Object 
Storage,](https://www.ibm.com/cloud/object-storage) 
[how-to-use-connector](https://developer.ibm.com/code/2018/08/16/installing-running-stocator-apache-spark-ibm-cloud-object-storage)
 
 Review comment:
   If this is more or less the equivalent of "S3 connector docs" for AWS, but 
for the IBM cloud, it could be OK. However I think this doc is a little more 
about what Spark directly supports, particularly through `hadoop-cloud`. (In 
any event I think you need to fix the anchors? they have commas in them.) Would 
this be more appropriate at 
https://github.com/apache/spark-website/blob/asf-site/third-party-projects.md ? 
it seems to refer to a third-party integration, not first-party cloud docs.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to