[
https://issues.apache.org/jira/browse/HADOOP-16794?focusedWorklogId=486306&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-486306
]
ASF GitHub Bot logged work on HADOOP-16794:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 18/Sep/20 17:38
Start Date: 18/Sep/20 17:38
Worklog Time Spent: 10m
Work Description: liuml07 commented on pull request #1875:
URL: https://github.com/apache/hadoop/pull/1875#issuecomment-694996949
@steveloughran I think we can merge this into branch-2.10.
This is very important fix. The failing tests are just about tests per my
previous debugging
[comment](https://github.com/apache/hadoop/pull/1875#discussion_r389237849).
The fix itself is reviewed and already in 3.3.0 releases. We have backported
this fix into our internal light-fork 6 months ago, and customers have not
complained since then. For the normal testing without per-bucket settings, the
test will pass.
Thoughts?
----------------------------------------------------------------
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: 486306)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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]
