steveloughran commented on issue #1823: HADOOP-16794 S3 Encryption key is not getting set properly during put operation. URL: https://github.com/apache/hadoop/pull/1823#issuecomment-582929516 So what is proposed is 1. If we have local SSE-KMS settings, use that 1. fall back to that on the source object What if we have local SSE-S3 enabled? would we want to switch for a simple rule: "if you have encryption set, renamed files pick it up; otherwise files encrypted with SSE-KMS keep their encryption" As @mukund-thakur's patch currently has "files encrypted with SSE-KMS retain that encryption setting when renamed, irrespective of your client settings" I think I prefer the one in mukund's patch as its simpler to explain. Encryption with SSE-KMS is "sticky"
---------------------------------------------------------------- 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] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
