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

Hudson commented on HADOOP-12292:
---------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9254 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9254/])
HADOOP-12292. Make use of DeleteObjects optional.  (Thomas Demoor via (stevel: 
rev 29ae25801380b94442253c4202dee782dc4713f5)
* 
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/scale/TestS3ADeleteManyFiles.java
* 
hadoop-tools/hadoop-aws/src/test/java/org/apache/hadoop/fs/s3a/scale/S3AScaleTestBase.java
* hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/Constants.java
* hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md
* hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
* hadoop-common-project/hadoop-common/CHANGES.txt
* hadoop-project/pom.xml
* 
hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AFileSystem.java


> Make use of DeleteObjects optional
> ----------------------------------
>
>                 Key: HADOOP-12292
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12292
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Thomas Demoor
>            Assignee: Thomas Demoor
>         Attachments: HADOOP-12292-001.patch, HADOOP-12292-002.patch, 
> HADOOP-12292-003.patch, HADOOP-12292-004.patch, HADOOP-12292-005.patch
>
>
> The {{DeleteObjectsRequest}} was not part of the initial S3 API, but was 
> added later. This patch allows one to configure s3a to replace each 
> multidelete request by consecutive single deletes. Evidently, this setting is 
> disabled by default as this causes slower deletes.
> The main motivation is to enable legacy S3-compatible object stores to make 
> the transition from s3n (which does not use multidelete) to s3a, fully 
> allowing the planned s3n deprecation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to