[
https://issues.apache.org/jira/browse/HADOOP-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135928#comment-15135928
]
Hudson commented on HADOOP-12292:
---------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9255 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9255/])
HADOOP-12292. Make use of DeleteObjects optional -move CHANGES.TXT (stevel: rev
1495ff979a47d17838218da77df4406f94b8227c)
* hadoop-common-project/hadoop-common/CHANGES.txt
> 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
> Fix For: 2.8.0
>
> Attachments: HADOOP-12292-001.patch, HADOOP-12292-002.patch,
> HADOOP-12292-003.patch, HADOOP-12292-004.patch, HADOOP-12292-005.patch,
> HADOOP-12292-branch-2-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)
