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 Thu, 20 Aug 2015 02:07:45 GMT

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

Steve Loughran commented on HADOOP-12292:
-----------------------------------------

core patch looks good. I can't help thinking, though, it may be cleaner to have a ".enable"
property, set to true by default.  having a .disable property makes it look like some retrospective
fix (which it may be, but we don't need to be blatant about it)

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

Mime
View raw message