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 "Mukund Thakur (Jira)" <ji...@apache.org> on 2024/06/06 21:34:00 UTC

[jira] [Updated] (HADOOP-18679) Add API for bulk/paged delete of files and objects

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

Mukund Thakur updated HADOOP-18679:
-----------------------------------
    Description: 
iceberg and hbase could benefit from being able to give a list of individual files to delete -files which may be scattered round the bucket for better read peformance.

Add some new optional interface for an object store which allows a caller to submit a list of paths to files to delete, where
the expectation is
 * if a path is a file: delete
 * if a path is a dir, outcome undefined
For s3 that'd let us build these into DeleteRequest objects, and submit, without any probes first.

{quote}Cherrypicking
{quote}
when cherrypicking, you must include
 * followup commit #6854
 * https://issues.apache.org/jira/browse/HADOOP-19196
 * test fixes HADOOP-19814 and HADOOP-19188

  was:
iceberg and hbase could benefit from being able to give a list of individual files to delete -files which may be scattered round the bucket for better read peformance. 

Add some new optional interface for an object store which allows a caller to submit a list of paths to files to delete, where
the expectation is
* if a path is a file: delete
* if a path is a dir, outcome undefined
For s3 that'd let us build these into DeleteRequest objects, and submit, without any probes first.

bq. Cherrypicking

when cherrypicking, you must include

* followup commit #6854
* test fixes HADOOP-19814 and HADOOP-19188



> Add API for bulk/paged delete of files and objects
> --------------------------------------------------
>
>                 Key: HADOOP-18679
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18679
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 3.3.5
>            Reporter: Steve Loughran
>            Assignee: Mukund Thakur
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.1
>
>
> iceberg and hbase could benefit from being able to give a list of individual files to delete -files which may be scattered round the bucket for better read peformance.
> Add some new optional interface for an object store which allows a caller to submit a list of paths to files to delete, where
> the expectation is
>  * if a path is a file: delete
>  * if a path is a dir, outcome undefined
> For s3 that'd let us build these into DeleteRequest objects, and submit, without any probes first.
> {quote}Cherrypicking
> {quote}
> when cherrypicking, you must include
>  * followup commit #6854
>  * https://issues.apache.org/jira/browse/HADOOP-19196
>  * test fixes HADOOP-19814 and HADOOP-19188



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org