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

ASF GitHub Bot commented on HADOOP-18679:
-----------------------------------------

steveloughran commented on PR #6726:
URL: https://github.com/apache/hadoop/pull/6726#issuecomment-2186233577

   + some interface getVersionForDeleteOperations() -> String to put on s3/abfs 
file status, the way we do for getEtag(), so you can extract version info 
without having to play class cast games, built with hadoop-aws and hadoop-azure 
on CP etc. 
   
   #3633 shows what's required there.




> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to