steveloughran opened a new pull request, #7316:
URL: https://github.com/apache/hadoop/pull/7316

   
   Add Iceberg core to the hadoop-aws test classpath.
   
   Iceberg is java17+ only, so this adds
   * A new test source path src/test/java17
   * A new profile "java-17-or-later" which includes this and declares the 
dependency on iceberg-core.
   
   The new test is ITestIcebergBulkDelete; it is parameterized Iceberg bulk 
delete enabled/disabled and s3a multipart delete enabled/disabled.
   
   There is a superclass contract test
     org.apache.fs.test.formats.AbstractIcebergDeleteTest
   To support future stores which implement bulk delete. This is currently a 
minimal superclass; all tests
   are currently in ITestIcebergBulkDelete
   
   
   ### How was this patch tested?
   
   Fun!
   
   1. Install java17
   1. Build locally this Iceberg PR: 
https://github.com/apache/iceberg/pull/10233
   1. switch hadoop builds to java8
   2. Verify that the aws module builds clean
   3. rebuild hadoop with java17
   4. run new test suite against S3 store
   
   Once we have iceberg PR 10233 merged in, we can merge this. Until then it 
doesn't currently compile as for testing unless we move to DynMethods there 
(maybe I should)
   
   
   ### 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?
   - [ ] 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)?
   - [ ] 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