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

ASF GitHub Bot commented on HADOOP-19331:
-----------------------------------------

zhouaoe opened a new pull request, #7314:
URL: https://github.com/apache/hadoop/pull/7314

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   Optimize the process by reducing some extra QPS.
   1 Create: Reduce one HEAD operation for coverage operations.
   2 Rename: Reduce an additional PUT operation. During the rename process, 
when determining whether to create a virtual empty directory, we check if the 
parent directory exists afterward. There is a bug in the original OSS code that 
leads to it creating the directory every time.
   3 Delete: Reduce one HEAD operation when creating a virtual parent 
directory. For the operation of creating a parent directory, use OSS server 
features to create it only when the target does not 
exist.(([https://www.alibabacloud.com/help/en/oss/user-guide/simple-upload?spm=a2c63.p38356.help-menu-31815.d_2_3_1_0.13644b78AT3Hyj)](https://www.alibabacloud.com/help/en/oss/user-guide/simple-upload?spm=a2c63.p38356.help-menu-31815.d_2_3_1_0.13644b78AT3Hyj%EF%BC%89))
   image
   
   ### How was this patch tested?
   1 Add new unit tests (UT)
   TestAliyunOSSFileSystemCreateFileListV1
   TestAliyunOSSFileSystemCreateFileListV2
   TestAliyunOSSFileSystemRenameFile
   2 Modify relevant integration tests
   TestAliyunOSSBlockOutputStream
   
   3 test integration tests and unit tests are executed
   mvn test -pl hadoop-tools/hadoop-aliyun
   
   image
   
   hadoop@96c5b859c556:~$ mvn test 
-Dtest=org.apache.hadoop.fs.aliyun.oss.TestAliyunOSSFileSystemCreateFileListV1 
-pl hadoop-tools/hadoop-aliyun
   
   image
   
   hadoop@96c5b859c556:~$ mvn test 
-Dtest=org.apache.hadoop.fs.aliyun.oss.TestAliyunOSSFileSystemCreateFileListV2 
-pl hadoop-tools/hadoop-aliyun
   
   image
   
   hadoop@96c5b859c556:~$ mvn test 
-Dtest=org.apache.hadoop.fs.aliyun.oss.TestAliyunOSSFileSystemDeleteFile -pl 
hadoop-tools/hadoop-aliyun
   
   image
   
   hadoop@96c5b859c556:~$ mvn test 
-Dtest=org.apache.hadoop.fs.aliyun.oss.TestAliyunOSSFileSystemRenameFile -pl 
hadoop-tools/hadoop-aliyun1s
   
   image
   
   
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [x] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   




> AliyunOSS :Optimize the process by reducing some extra QPS.
> -----------------------------------------------------------
>
>                 Key: HADOOP-19331
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19331
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/oss
>            Reporter: zhouao
>            Priority: Major
>              Labels: pull-request-available
>
> AliyunOSSConnector has not been updated for a long time. It implements basic 
> functionality,  but its performance is not optimal, especially in terms of 
> QPS requests. It generates a  significant number of invalid QPS, which 
> increases the cost on the storage service side and  also reduces the 
> efficiency on the connector side. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to