[
https://issues.apache.org/jira/browse/HADOOP-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732657#comment-16732657
]
Weiwei Yang commented on HADOOP-15323:
--------------------------------------
Hi [~wujinhu]
Thanks for the clarification, in that case, the fallback code is less thing to
concern. Since there is no other alternative way, I am OK with this approach.
But could you add some DEBUG log in the catch clause to help debugging?
You don't need to add deprecated annotation in the code, instead could you
please add some note in documentation \{{index.md}}? Instead of removing the
property, you can add a note message: this property is deprecated and will be
removed in further version.
BTW, which branch should this be committed to? As this is a behavior change, do
we need it in branch-2.x?
Thanks
> AliyunOSS: Improve copy file performance for AliyunOSSFileSystemStore
> ---------------------------------------------------------------------
>
> Key: HADOOP-15323
> URL: https://issues.apache.org/jira/browse/HADOOP-15323
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/oss
> Affects Versions: 2.10.0, 3.2.0, 3.1.1, 2.9.2, 3.0.3, 3.3.0
> Reporter: wujinhu
> Assignee: wujinhu
> Priority: Major
> Attachments: HADOOP-15323.001.patch, HADOOP-15323.002.patch
>
>
> Aliyun OSS will support shallow copy which means server will only copy
> metadata when copy object operation occurs.
> With shallow copy, we can use copyObject api instead of multi-part copy api
> if we do not change object storage type & encryption type & source object is
> uploaded by Put / Multipart upload api.
> We will try to use copyObject api, and check result. If shallow copy disabled
> for this object, then we will use multipart copy. So, I will remove
> fs.oss.multipart.upload.threshold configuration.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
