hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12292) Make use of DeleteObjects optional
Date Sat, 06 Feb 2016 15:07:39 GMT

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

Steve Loughran commented on HADOOP-12292:

+1, committed to trunk

I'm going to quickly see if I can backport to branch-2/2.8, which means the patch need to
be tuned for the fact that HADOOP-11684 isn't in there —the diff won't apply directly

> 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

View raw message