[
https://issues.apache.org/jira/browse/HADOOP-13131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281921#comment-15281921
]
Chris Nauroth commented on HADOOP-13131:
----------------------------------------
Thank you for the updates in patch v002. I did a successful full test run in
combination with HADOOP-13113 to make sure the new tests are parallel-friendly.
bq. Anyway, if the implementation is ignoring the header then this test will
fail
Thank you. I see the problem now. I can't think of a great solution to this,
other than skipping the test with additional build flags or configuration
properties if it's really important.
bq. Actually, I should do it for a copy() too, shouldn't it?
That's a good point. Full test coverage would add coverage of copy, and also
use of {{fs.s3a.fast.upload}}.
> 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
>
> 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]
