Skip to content
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

Does the new version support JDK17 and JDK21? #32822

Closed
NicknameZZ opened this issue Sep 10, 2024 · 6 comments
Closed

Does the new version support JDK17 and JDK21? #32822

NicknameZZ opened this issue Sep 10, 2024 · 6 comments

Comments

@NicknameZZ
Copy link

Does version 5.4 or 5.5 support JDK17 and JDK21?

@linghengqian
Copy link
Member

  • CI covers JDK8 - JDK22, so the answer to your question is obviously yes.
  • By the way, JDK24 currently has breaking changes, which is not something that shardingsphere can solve, and you need to wait for the OracleLabs side to synchronize the changes.

@linghengqian
Copy link
Member

@NicknameZZ
Copy link
Author

By the way, is the 5.5.0/5.4.1 compatible with JDK8?

@linghengqian
Copy link
Member

By the way, is the 5.5.0/5.4.1 compatible with JDK8?

  • For any shardingsphere version, you need to compile with JDK11-JDK22, but the product can always run on JDK 8. This is because JDK11 is required by Antlr 4 compiler. Antlr 5 does not provide Java support yet, and ShardingSphere does not use Antlr 5 to write rules for parsing SQL.
  • The only exception is GraalVM Native Image. To use ShardingSphere JDBC under GraalVM Native Image, you need GraalVM CE For JDK 22.0.2 or higher to compile the corresponding product, which is a requirement of apache/hive. According to the release cycle of OracleLabs, ShardingSphere will only support compilation through GraalVM CE For JDK 23 or GraalVM CE For JDK 24 in the next few months. GraalVM CE For JDK 23 has very breaking changes around the GraalVM Native Image.

Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

@linghengqian
Copy link
Member

  • Issue closed due to no response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants