[jira] [Commented] (KAFKA-12358) Migrate to Java 11
[ https://issues.apache.org/jira/browse/KAFKA-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288436#comment-17288436 ] Dongjin Lee commented on KAFKA-12358: - Hi Ismael, Thanks for your kind advice. Of course, I don't expect we can do this migration in the near future. The reason why I created this issue is for calling attention to the relationship with the Jetty project. Let's wait for the community's feedback. Thanks again! > Migrate to Java 11 > -- > > Key: KAFKA-12358 > URL: https://issues.apache.org/jira/browse/KAFKA-12358 > Project: Kafka > Issue Type: Improvement >Reporter: Dongjin Lee >Assignee: Dongjin Lee >Priority: Major > Labels: needs-kip > > I found this problem when I was working on > [KAFKA-12324|https://issues.apache.org/jira/browse/KAFKA-12324]. > As of present, Kafka Connect and Trogdor are using Jetty 9. Although Jetty's > stable release is 9.4, the Jetty community is now moving their focus to Jetty > 10 and 11, which requires Java 11 as a prerequisite. To minimize potential > security vulnerability, Kafka should migrate into Java 11 + Jetty 11 as soon > as Jetty 9.4 reaches the end of life. As a note, [Jetty 9.2 reached End of > Life in March > 2018|https://www.eclipse.org/lists/jetty-announce/msg00116.html] and 9.3 also > did in [February > 2020|https://www.eclipse.org/lists/jetty-announce/msg00140.html]. > In other words, the necessity of moving to Java 11 is heavily affected by > Jetty's maintenance plan. Jetty 9.4 seems like still be supported for a > certain period of time, but it is worth being aware of these relationships > and having a migration plan beforehand. > For the java-scala compatibility, we have no issue. The recommended Scala > versions to Java 11 are 2.13.0 and 2.12.4, and we are already using the later > version. See: > https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-12358) Migrate to Java 11
[ https://issues.apache.org/jira/browse/KAFKA-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288432#comment-17288432 ] Ismael Juma commented on KAFKA-12358: - Requiring Java 11 is a major decision and requires a KIP. A large percentage of users is still on Java 8, so not sure we can do this right now. Clients, in particular, will have to be Java 8 for a few more years, I'd imagine. The broker and connect could potentially require Java 11 sooner, but even that will probably have to wait until Apache Kafka 4.0 (when we plan to remove ZK support altogether). > Migrate to Java 11 > -- > > Key: KAFKA-12358 > URL: https://issues.apache.org/jira/browse/KAFKA-12358 > Project: Kafka > Issue Type: Improvement >Reporter: Dongjin Lee >Assignee: Dongjin Lee >Priority: Major > Labels: needs-kip > > I found this problem when I was working on > [KAFKA-12324|https://issues.apache.org/jira/browse/KAFKA-12324]. > As of present, Kafka Connect and Trogdor are using Jetty 9. Although Jetty's > stable release is 9.4, the Jetty community is now moving their focus to Jetty > 10 and 11, which requires Java 11 as a prerequisite. To minimize potential > security vulnerability, Kafka should migrate into Java 11 + Jetty 11 as soon > as Jetty 9.4 reaches the end of life. As a note, [Jetty 9.2 reached End of > Life in March > 2018|https://www.eclipse.org/lists/jetty-announce/msg00116.html] and 9.3 also > did in [February > 2020|https://www.eclipse.org/lists/jetty-announce/msg00140.html]. > In other words, the necessity of moving to Java 11 is heavily affected by > Jetty's maintenance plan. Jetty 9.4 seems like still be supported for a > certain period of time, but it is worth being aware of these relationships > and having a migration plan beforehand. > For the java-scala compatibility, we have no issue. The recommended Scala > versions to Java 11 are 2.13.0 and 2.12.4, and we are already using the later > version. See: > https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KAFKA-12358) Migrate to Java 11
[ https://issues.apache.org/jira/browse/KAFKA-12358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17288430#comment-17288430 ] Dongjin Lee commented on KAFKA-12358: - https://github.com/apache/kafka/pull/10176 Here is a draft implementation of Java 11 migration. If anyone encounters this issue, please notify me - then I will submit the KIP. Thanks in advance. > Migrate to Java 11 > -- > > Key: KAFKA-12358 > URL: https://issues.apache.org/jira/browse/KAFKA-12358 > Project: Kafka > Issue Type: Improvement >Reporter: Dongjin Lee >Assignee: Dongjin Lee >Priority: Major > Labels: needs-kip > > I found this problem when I was working on > [KAFKA-12324|https://issues.apache.org/jira/browse/KAFKA-12324]. > As of present, Kafka Connect and Trogdor are using Jetty 9. Although Jetty's > stable release is 9.4, the Jetty community is now moving their focus to Jetty > 10 and 11, which requires Java 11 as a prerequisite. To minimize potential > security vulnerability, Kafka should migrate into Java 11 + Jetty 11 as soon > as Jetty 9.4 reaches the end of life. As a note, [Jetty 9.2 reached End of > Life in March > 2018|https://www.eclipse.org/lists/jetty-announce/msg00116.html] and 9.3 also > did in [February > 2020|https://www.eclipse.org/lists/jetty-announce/msg00140.html]. > In other words, the necessity of moving to Java 11 is heavily affected by > Jetty's maintenance plan. Jetty 9.4 seems like still be supported for a > certain period of time, but it is worth being aware of these relationships > and having a migration plan beforehand. > For the java-scala compatibility, we have no issue. The recommended Scala > versions to Java 11 are 2.13.0 and 2.12.4, and we are already using the later > version. See: > https://docs.scala-lang.org/overviews/jdk-compatibility/overview.html -- This message was sent by Atlassian Jira (v8.3.4#803005)