[
https://issues.apache.org/jira/browse/HADOOP-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-12292:
------------------------------------
Attachment: HADOOP-12292-004.patch
This patch makes no change to the src/main of patch -003, just subclasses the
{{TestS3ADeleteManyFiles}} test to add a test {{TestS3ADeleteFilesOneByOne}}
for singular operation.
In the process of running these, the s3a test suite alone proved enough to
trigger surefire timeouts for me. I've had to make the surefire timeout in the
hadoop build something configurable; surprised it hadn't been done already.
I've done all the S3 tests; a transient failure of
{{TestS3AFileSystemContract.testLSRootDir}} which I couldn't repeat was the
only issue.
Let's see what jenkins says, but otherwise the patch LGTM
> 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
>
>
> 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)
