[
https://issues.apache.org/jira/browse/HADOOP-16794?focusedWorklogId=492573&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-492573
]
ASF GitHub Bot logged work on HADOOP-16794:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 29/Sep/20 17:25
Start Date: 29/Sep/20 17:25
Worklog Time Spent: 10m
Work Description: steveloughran commented on pull request #1875:
URL: https://github.com/apache/hadoop/pull/1875#issuecomment-700862736
3.2 and 3.3 have diverged so much in s3a. I tried a bit of a backport and
gave up.
Now, internally, CDH 7/CDP is built on the 3.1+ codebase, with much of the
s3a changes backported. But its not always easy, and was done as code was added
* mockito changes break tests, even though things compile
* commons-lang is trouble
* some things (multipart uploader API) haven't gone back
I'm reluctant to replicate the same problems here.
What would be good
* do an AWS SDK update everywhere
* on older releases, turn off tests we know are flakly/fixed with big
changes on later branches
* backport FS API Changes (openFile() in particular) so that code can
compile more broadly against them. That doesn't mean backporting all the
speedups behind the scenes, just the API
----------------------------------------------------------------
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: 492573)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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]
