HDDS-11052. HttpFS fails to start when compiled for Java 17 #6854
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
HttpFS fails to start when compiled by and for Java 17:
Excerpt from HttpFS log:
HttpServer2from HDDS instead of Hadoop.HttpServer2and HttpFS to Jersey 2, which Ozone already uses in S3 Gateway. Parts of this change are taken from [WIP] HADOOP-15984. Update jersey from 1.19 to 2.x hadoop#763, thanks @aajisaka, since these components were originally adapted from Hadoop.https://issues.apache.org/jira/browse/HDDS-11052
How was this patch tested?
Compiled with and for Java 17:
https://github.com/adoroszlai/ozone/actions/runs/9741132878/job/26879699266#step:7:1
and ran HA-unsecure acceptance test, including HttpFS tests, with Java 17:
https://github.com/adoroszlai/ozone/actions/runs/9741132878/job/26880396757#step:6:1084
Regular CI:
https://github.com/adoroszlai/ozone/actions/runs/9746424125