Hi, all, Thanks a lot for the pointers. Very useful and glad to see it in motion!
One thing I would like to consider is: except for some core modules that all Beam code uses, can we start marking individual SDKs as JDK11 compatible? For example, we are using DataflowRunner and Kafka, is it possible to make beam-runners-google-cloud-dataflow-java and beam-sdks-java-io-kafka JDK11 compatible first? I think that what I am proposing is to start a list of JDK11 compatible SDKs/packages first, and gradually populate this list till all java code is JDK8 and JDK11 compatible. Thanks! -Yi On Tue, Apr 9, 2019 at 3:00 PM Ahmet Altay <al...@google.com> wrote: > Most recently +Pablo Estrada <pabl...@google.com> and +Michał Walenia > <michal.wale...@polidea.com> were working on Java 11 related JIRAs. They > may have more context. > > On Tue, Apr 9, 2019 at 1:22 PM Maximilian Michels <m...@apache.org> wrote: > >> Hi Yi, >> >> That's a great question. Beam is still on Java 8 at the moment. There is >> a JIRA issue for making Beam compatible with Java 11: >> https://issues.apache.org/jira/browse/BEAM-2530 >> >> As you can read in the issue, the upcoming Beam 2.12.0 has experimental >> support for Java 11. That said, there is still code that needs a major >> overhaul, e.g. automatic staging of pipeline jars >> (https://issues.apache.org/jira/browse/BEAM-5495). >> >> I hope we can achieve proper Java 11 compatibility in the next releases. >> Perhaps somebody else can give further insight into how much work is left. >> >> Thanks, >> Max >> >> On 09.04.19 22:07, Yi Pan wrote: >> > Hi, everyone, >> > >> > I checked out the latest Beam code and seems that the document still >> > says "JDK8". Is there any plan to officially support JDK11? >> > >> > Thanks a lot! >> > >> > -Yi >> >
