-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate Docker images and CI to Java 17 #14355
Conversation
/pulsarbot rerun-failure-checks |
1 similar comment
/pulsarbot rerun-failure-checks |
/pulsarbot rerun-failure-checks |
The pr had no activity for 30 days, mark with Stale label. |
@nicoloboschi Please rebase this PR |
40dc096
to
1880873
Compare
/pulsarbot rerun-failure-checks |
Hi nicoloboschi, I am definitely a latecomer to this issue, but I think we could also support java17 build as well as this java17 runtime support. I added this java17 build support and created a pip here, #15207. I can help with upgrading the build for java17 and adding the different jdk compatibility tests (if not done yet). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Motivation
The goal is to run Pulsar using JDK17 at runtime, benefitting from the latest JVM performance improvements and features.
In order to do that we need to run all the tests using JDK17.
The goal is NOT to deprecate JDK8 or JDK11 runtime compatibility. The java compiler release flag doesn't change.
Modifications
Verifying this change
All the CI jobs are passing
Manual tests are encouraged, mainly around
pulsar-io
connectors since we don't have integration tests for all the connectors.Documentation
doc
Added the support for JDK17 in the installation page.