Hey Dane, Thanks for bringing this up again.
In the dev-list thread you referred to I hesitated to drop Java <17, but it is time. We see several projects that are moving past Java 8, and in the process are also dropping Java 11 since it is not supported anymore <https://www.oracle.com/java/technologies/java-se-support-roadmap.html>. I echo'd this on the Iceberg dev list, and also suggested this with Avro 1.12 <https://lists.apache.org/thread/6vbd3w5qk7mpb5lyrfyf2s0z1cymjt5w>. Kind regards, Fokko Op do 25 apr 2024 om 22:02 schreef Dane Pitkin <d...@voltrondata.com.invalid >: > Hi all, > > I would like to revisit the discussion of dropping Java 8 (and maybe 11) > from Arrow's Java implementation. See GH issue[1] below. This was also > discussed in the last Arrow community sync meeting on 2024-04-24. > > For context, this was discussed[2] last year on this mailing list. We > decided to revisit the discussion around the June 2024 release (Arrow v17). > The timing coincides with the initial release of Apache Spark 4.0.0, which > drops both Java 8 and 11 support. > > For background, we chose not to drop Java 8 support last year because Arrow > is seen as a low level library that should support as many environments as > possible. Nowadays, we see more enthusiasm for dropping Java 8 (and 11) as > exemplified by Apache Spark as well as Apache Iceberg[3]. > > Is it time to consider dropping Java 8? Should we drop Java 11 and skip > straight to Java 17 as our minimum version? What implications do we need to > be aware of? > > Thanks, > Dane > > [1]https://github.com/apache/arrow/issues/38051 > [2]https://lists.apache.org/thread/s07jx58yw4mkl54t3bkggnyg0sftcrr8 > [3]https://lists.apache.org/thread/ntrk2thvsg9tdccwd4flsdz9gg743368 >
