[ 
https://issues.apache.org/jira/browse/HADOOP-13887?focusedWorklogId=621987&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-621987
 ]

ASF GitHub Bot logged work on HADOOP-13887:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jul/21 12:50
            Start Date: 13/Jul/21 12:50
    Worklog Time Spent: 10m 
      Work Description: mukund-thakur commented on pull request #2706:
URL: https://github.com/apache/hadoop/pull/2706#issuecomment-879058793


   > Interesting you see those errors since they should be skipped if CSE is 
enabled, I'll try to see what's wrong.
   
   No that was without enabling CSE as said above. 
   
   Now I am trying to run the tests after enabling CSE. And the first issue I 
see is 
   `[ERROR] Tests run: 17, Failures: 0, Errors: 17, Skipped: 0, Time elapsed: 
22.59 s <<< FAILURE! - in 
org.apache.hadoop.fs.contract.s3a.ITestS3AContractMultipartUploader
   [ERROR] 
testMultipartUpload(org.apache.hadoop.fs.contract.s3a.ITestS3AContractMultipartUploader)
  Time elapsed: 6.382 s  <<< ERROR!
   java.lang.UnsupportedOperationException: Multi-part uploader not supported 
for Client side encryption.
        at 
org.apache.hadoop.fs.s3a.S3AFileSystem.createMultipartUploader(S3AFileSystem.java:5396)
        at 
org.apache.hadoop.fs.s3a.S3AFileSystem.createMultipartUploader(S3AFileSystem.java:249)
        at 
org.apache.hadoop.fs.contract.AbstractContractMultipartUploaderTest.setup(AbstractContractMultipartUploaderTest.java:92)
        at 
org.apache.hadoop.fs.contract.s3a.ITestS3AContractMultipartUploader.setup(ITestS3AContractMultipartUploader.java:115)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   `
   
   This should have been skipped rather that failed. 
   
   I will update on how the rest goes. 


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 621987)
    Time Spent: 6h 10m  (was: 6h)

> Encrypt S3A data client-side with AWS SDK (S3-CSE)
> --------------------------------------------------
>
>                 Key: HADOOP-13887
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13887
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.8.0
>            Reporter: Jeeyoung Kim
>            Assignee: Igor Mazur
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: HADOOP-13887-002.patch, HADOOP-13887-007.patch, 
> HADOOP-13887-branch-2-003.patch, HADOOP-13897-branch-2-004.patch, 
> HADOOP-13897-branch-2-005.patch, HADOOP-13897-branch-2-006.patch, 
> HADOOP-13897-branch-2-008.patch, HADOOP-13897-branch-2-009.patch, 
> HADOOP-13897-branch-2-010.patch, HADOOP-13897-branch-2-012.patch, 
> HADOOP-13897-branch-2-014.patch, HADOOP-13897-trunk-011.patch, 
> HADOOP-13897-trunk-013.patch, HADOOP-14171-001.patch, S3-CSE Proposal.pdf
>
>          Time Spent: 6h 10m
>  Remaining Estimate: 0h
>
> Expose the client-side encryption option documented in Amazon S3 
> documentation  - 
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
> Currently this is not exposed in Hadoop but it is exposed as an option in AWS 
> Java SDK, which Hadoop currently includes. It should be trivial to propagate 
> this as a parameter passed to the S3client used in S3AFileSystem.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to