[
https://issues.apache.org/jira/browse/HADOOP-13131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-13131:
------------------------------------
Attachment: HADOOP-13131-003.patch
Patch 003
Examining the object metadata to verify that encryption is set on a write, and
set during a rename (copy) operation. Tests can be disabled, with the
documentation covering this.
I also took the opportunity to clean up the tests somewhat, with a file
S3ATestConstants for the various constants, a new abstract class
AbstractS3ATestBase which is an FSContract test set up to auto-create the S3
contract, plus some helpers. This is intended to be the base for future S3A
Tests
> add tests to verify that s3a supports SSE-S3 encryption
> -------------------------------------------------------
>
> Key: HADOOP-13131
> URL: https://issues.apache.org/jira/browse/HADOOP-13131
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.7.2
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-13131-001.patch, HADOOP-13131-002.patch,
> HADOOP-13131-003.patch
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Although S3A claims to support server-side S3 encryption (and does, if you
> set the option), we don't have any test to verify this. Of course, as the
> encryption is transparent, it's hard to test.
> Here's what I propose
> # a test which sets encryption = AES256; expects things to work as normal.
> # a test which sets encyption = DES and expects any operation creating a file
> or directory to fail with a 400 "bad request" error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
