[
https://issues.apache.org/jira/browse/HADOOP-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303346#comment-15303346
]
Ling Zhou commented on HADOOP-12756:
------------------------------------
Hi everyone. Our patch is updated. The code is after the latest hadoop trunk.
1. OSS keys are passed via the test/resources/auth-keys.xml file, the same way
as S3A.
2. Module is renamed to hadoop-aliyun.
3. Since httpclient in hadoop trunk is updated to 4.5.2, the dependency
conflict issue is solved.
We have prepared individual Aliyun OSS account to test this patch. But how will
the account info and other test properties be configured and tests can be
properly triggered?
Thank you for your response.
> Incorporate Aliyun OSS file system implementation
> -------------------------------------------------
>
> Key: HADOOP-12756
> URL: https://issues.apache.org/jira/browse/HADOOP-12756
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Affects Versions: 2.8.0
> Reporter: shimingfei
> Assignee: shimingfei
> Attachments: HADOOP-12756-v02.patch, HCFS User manual.md, OSS
> integration.pdf, OSS integration.pdf
>
>
> Aliyun OSS is widely used among China’s cloud users, but currently it is not
> easy to access data laid on OSS storage from user’s Hadoop/Spark application,
> because of no original support for OSS in Hadoop.
> This work aims to integrate Aliyun OSS with Hadoop. By simple configuration,
> Spark/Hadoop applications can read/write data from OSS without any code
> change. Narrowing the gap between user’s APP and data storage, like what have
> been done for S3 in Hadoop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
