[jira] [Commented] (FLINK-10865) Implement Flink's own Aliyun OSS filesystem

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16689419#comment-16689419 ] 

ASF GitHub Bot commented on FLINK-10865:
----------------------------------------

wujinhu opened a new pull request #7123: [FLINK-10865] Add Aliyun OSS file systems without Hadoop dependencies
URL: https://github.com/apache/flink/pull/7123
 
 
   
   ## What is the purpose of the change
   
   This PR will add an implementation of a file system that read from & write to Aliyun OSS so that users can use OSS with Flink without depending on Hadoop. In this way, users will find it is more easily to use OSS with Flink now.
   
   This implementation wraps **AliyunOSSFileSystem** and shade its dependencies. However, the wrapped jar is not in Flink's lib directory,  users need to copy the jar which built in **opt** directory to **lib** directory.
   
   
   ## Brief change log
   
   - Adds **flink-filesystems/flink-oss-fs-hadoop**
   
   
   ## Verifying this change
   
   This implementation adds some tests to test instantiation and some reads & writes & lists operations(test communications with Aliyun OSS). However, in order to run these tests, someone need to have his own Aliyun access key id and access key secret. Then, set environment variables below：
   `export ARTIFACTS_OSS_ENDPOINT=<Aliyun OSS endpoint to connect to>`
   `export ARTIFACTS_OSS_BUCKET=<Your bucket>`
   `export ARTIFACTS_OSS_ACCESS_KEY=<Your access key id>`
   `export ARTIFACTS_OSS_SECRET_KEY=<Your access secret>`
   
   These tests are skipped by default.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (**yes** / no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (**yes** / no / don't know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (**yes** / no)
     - If yes, how is the feature documented? (not applicable / **docs** / JavaDocs / not documented)
   

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


> Implement Flink's own Aliyun OSS filesystem
> -------------------------------------------
>
>                 Key: FLINK-10865
>                 URL: https://issues.apache.org/jira/browse/FLINK-10865
>             Project: Flink
>          Issue Type: New Feature
>          Components: filesystem-connector
>    Affects Versions: 1.6.2
>            Reporter: wujinhu
>            Priority: Major
>              Labels: pull-request-available
>
> Aliyun OSS is widely used among China’s cloud users, and Hadoop supports Aliyun OSS since 2.9.1. 
> Open this jira to wrap AliyunOSSFileSystem in flink(similar to s3 support), so that user can read from & write to OSS more easily in flink. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)