[
https://issues.apache.org/jira/browse/HADOOP-19050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17825820#comment-17825820
]
ASF GitHub Bot commented on HADOOP-19050:
-----------------------------------------
steveloughran commented on PR #6544:
URL: https://github.com/apache/hadoop/pull/6544#issuecomment-1992515204
You're right there is no rename; copy is all there is. So that is not
available yet? Hmmm. This isn't ready for production yet is it? Let us keep it
in trunk for now. The other strategy would be to do a feature branch for it,
which has mixed benefits. Good: isolated from other work. Bad: isolated from
other work. So far the changes are minimal enough it is not a problem.
Now that I am working on a bulk delete API targeting Iceberg and similar
where the caller congener write a bulk delete call across the bucket; currently
in S3AFS we only do bulk deletes down a "directory tree" either in delete or
incrementally during rename(). In both of these cases there is already no
guarantees that your system will be left in a nice state if you don't have the
permissions to do things.
Regarding testing, when you think it is ready for others to play with a
section in testing.md on how to get set up for this would be good. Well I don't
personally have plans for that, maybe I could persuade colleagues. I tried to
test a lot of the other corner cases.
> Add S3 Access Grants Support in S3A
> -----------------------------------
>
> Key: HADOOP-19050
> URL: https://issues.apache.org/jira/browse/HADOOP-19050
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/s3
> Affects Versions: 3.4.0
> Reporter: Jason Han
> Assignee: Jason Han
> Priority: Minor
> Labels: pull-request-available
>
> Add support for S3 Access Grants
> (https://aws.amazon.com/s3/features/access-grants/) in S3A.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
