steveloughran opened a new pull request, #4675: URL: https://github.com/apache/hadoop/pull/4675
This is the commit chain of feature-HADOOP-18028-s3a-prefetch rebased to trunk and with a fixup at the end. I intend to apply this chain to the feature branch with a goal of a squash and merge of the branch into trunk ASAP, with all final work done on trunk ### How was this patch tested? s3 london, params `-Dparallel-tests -DtestsThreadCount=8 -Dscale` all new failures reported * [HADOOP-18386](https://issues.apache.org/jira/browse/HADOOP-18386) ITestS3SelectLandsat timeout after 10 minutes. surfaces in trunk too. * [HADOOP-18384](https://issues.apache.org/jira/browse/HADOOP-18384) ITestS3AFileSystemStatistic failure in prefetch feature branch * [HADOOP-18385](https://issues.apache.org/jira/browse/HADOOP-18385) ITestS3ACannedACLs failure; not in a span. I don't believe any are related, rather that changing the #of tests triggered latent issues surfacing from different states of the jvm before each suite, or, in the case of the landsat one, some change in the endpoint. ### 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]
