[
https://issues.apache.org/jira/browse/HADOOP-19801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Minack updated HADOOP-19801:
-----------------------------------
Description:
A non-empty directory, as well as a directory where its emptiness is unknown,
is deleted by listing all contained files (or objects with matching key
prefix), then deleting those files (objects) in bulk delete requests, and
finally deleting the (then) empty directory itself.
The recursive deletion of objects is not needed for S3 endpoints that support
deleting non-empty directories (or path prefixes).
For example: The [VAST S3 endpoint supports deleting non-empty
directories|https://kb.vastdata.com/documentation/docs/using-trash-folder-for-s3-objects-6]
with a single request. Such a feature can only be fully leveraged if
{{hadoop-aws}} coupd skip the recursive deletion.
was:
A non-empty directory, as well as a directory where its emptiness is unknown,
is deleted by listing all contained files (or objects with matching key
prefix), then deleting those files (objects) in bulk delete requests, and
finally deleting the (then) empty directory itself.
The recursive deletion of objects is not needed for S3 endpoints that support
deleting non-empty directories (or path prefixes).
For example: The [VAST S3 endpoint supports deleting non-empty
directories|https://support.vastdata.com/s/document-item?bundleId=vast-cluster-administrator-s-guide4.7&topicId=managing-access-protocols/s3-object-storage-protocol/s3-client-features.html&_LANG=enus]
with a single request. Such a feature can only be fully leveraged if
{{hadoop-aws}} coupd skip the recursive deletion.
> Allow to skip recursive file deletion for non-empty directory
> -------------------------------------------------------------
>
> Key: HADOOP-19801
> URL: https://issues.apache.org/jira/browse/HADOOP-19801
> Project: Hadoop Common
> Issue Type: New Feature
> Components: hadoop-aws
> Reporter: Enrico Minack
> Priority: Major
>
> A non-empty directory, as well as a directory where its emptiness is unknown,
> is deleted by listing all contained files (or objects with matching key
> prefix), then deleting those files (objects) in bulk delete requests, and
> finally deleting the (then) empty directory itself.
> The recursive deletion of objects is not needed for S3 endpoints that support
> deleting non-empty directories (or path prefixes).
> For example: The [VAST S3 endpoint supports deleting non-empty
> directories|https://kb.vastdata.com/documentation/docs/using-trash-folder-for-s3-objects-6]
> with a single request. Such a feature can only be fully leveraged if
> {{hadoop-aws}} coupd skip the recursive deletion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
