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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/07/30 12:51:00 UTC
[jira] [Updated] (HADOOP-17822) fs.s3a.acl.default not working
after S3A Audit feature added
[ https://issues.apache.org/jira/browse/HADOOP-17822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HADOOP-17822:
------------------------------------
Labels: pull-request-available (was: )
> fs.s3a.acl.default not working after S3A Audit feature added
> ------------------------------------------------------------
>
> Key: HADOOP-17822
> URL: https://issues.apache.org/jira/browse/HADOOP-17822
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After HADOOP-17511 the fs.s3a.acl.default propperty isn't being passed through to S3 PUT/COPY requests.
> The new RequestFactory is being given the acl values from the S3A FS instance, but the factory is being created before the acl settings are loaded from the configuration.
> Fix, and ideally, test (if the getXAttr lets us see this now)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org