[
https://issues.apache.org/jira/browse/HADOOP-16794?focusedWorklogId=486620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-486620
]
ASF GitHub Bot logged work on HADOOP-16794:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Sep/20 06:38
Start Date: 20/Sep/20 06:38
Worklog Time Spent: 10m
Work Description: liuml07 commented on pull request #1875:
URL: https://github.com/apache/hadoop/pull/1875#issuecomment-695751941
@steveloughran Given the failing tests are not related to the fix per se, do
you think it's fine if I backport the fix only without including tests into
`branch-2.10`? I think it would be nice to include this in new pending release
2.10.1.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 486620)
Time Spent: 0.5h (was: 20m)
> S3A reverts KMS encryption to the bucket's default KMS key in rename/copy
> -------------------------------------------------------------------------
>
> Key: HADOOP-16794
> URL: https://issues.apache.org/jira/browse/HADOOP-16794
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.2.1
> Reporter: Mukund Thakur
> Assignee: Mukund Thakur
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.3.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When using (bucket-level) S3 Default Encryption with SSE-KMS and a CMK, all
> files uploaded via the HDFS {{FileSystem}} {{s3a://}} scheme receive the
> wrong encryption key, always falling back to the region-specific AWS-managed
> KMS key for S3, instead of retaining the custom CMK.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
