[
https://issues.apache.org/jira/browse/KUDU-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901632#comment-17901632
]
Zoltan Chovan commented on KUDU-3630:
-------------------------------------
[~wendigo] Kudu is currently built with gradle 7.6, this version of gradle is
only supporting up to JDK19 [1], are you using the build kudu-client.jar in an
application that is built with JDK 24?
Please note, that the Kudu project doesn't even currently claim to fully
support JDK 19. All tests are still run on JDK 8.
[1] https://docs.gradle.org/current/userguide/compatibility.html
> Kudu uses deprecated SecurityManager features
> ---------------------------------------------
>
> Key: KUDU-3630
> URL: https://issues.apache.org/jira/browse/KUDU-3630
> Project: Kudu
> Issue Type: Improvement
> Reporter: Mateusz Gajewski
> Priority: Major
>
> JDK 18 deprecated Subject.doAs in favour of a new method Subject.callAs. JDK
> 23 requires -Djava.security.manager=allow to use Kudu client, while JDK 24
> removes the Security Manager altogether which makes Kudu client impossible to
> use.
> Kudu client uses deprecated APIs in places like:
> https://github.com/apache/kudu/blob/da6211df5f8df0c53ceedd542b61634f3bab7205/java/kudu-client/src/main/java/org/apache/kudu/client/Negotiator.java#L955
> This can be solved using reflective access as done by other projects, like
> Kafka's shim: https://github.com/apache/kafka/pull/16522
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
