holdenk opened a new pull request #3312:
URL: https://github.com/apache/hadoop/pull/3312


   ### Description of PR
   
   Add support for user specified content encoding for S3A.
   
   ### How was this patch tested?
   
   Run existing unit tests, new integration test, and run S3A integration tests 
in us-east-2. Added some small changes to S3 integration tests to skip 
encryption tests when key is null or alg is null (I believe this matches the 
original intention given the use of `StringUtils.isBlank` for skipping the 
test).
   
   ### For code changes:
   
   - [ X ] Does the title or this PR starts with the corresponding JIRA issue 
id (e.g. 'HADOOP-17799. Your PR title ...')?
   - [ X ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?:
   (us-east-2 ran with `holden@a61a514145cb:~/hadoop/hadoop-tools/hadoop-aws$ 
mvn  clean verify -Dnon-auth -Ds3guard` inside of the docker dev instance)
   Notable failures, which existed without the change are 
`org.apache.hadoop.fs.s3a.ITestS3AMiscOperations` (namely ` checksums of empty 
files expected:<etag: "5e3037f6b23642c732f1b705db9dcf17"> but was:<etag: 
"e5321d4514ae69ccf36995e8e1ac846f">`) . I can dig into this more if this isn't 
expected/flaky.
   - [ N/A ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ N/A ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


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



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

Reply via email to