You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/02/05 22:20:39 UTC

[jira] [Updated] (HADOOP-12292) Make use of DeleteObjects optional

     [ https://issues.apache.org/jira/browse/HADOOP-12292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Loughran updated HADOOP-12292:
------------------------------------
    Status: Open  (was: Patch Available)

> 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
>
>
> 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)