Now that we have removed support for Java 8, I wanted to start a discussion about dropping support for Java 11 as well since it is also pretty old, and making 17 the minimum supported version. There are a lot of nice language features with newer java versions, so getting a bit more aggressive about refreshing the minimum supported version periodically would allow us to begin to take advantage of these improvements, and would also reduce the number of tests we need to run in the CI pipeline.
I am aware of a couple of things to consider in this discussion, the first being that Hadoop does not yet support Java 17 as a runtime. Though it does seem to be planned https://issues.apache.org/jira/browse/HADOOP-17177, I am unsure of the timeline for it to be released, so we might need to wait until this happens before we can totally remove it. I am starting another thread to survey Hadoop usage to see if this actually needs to be a blocker or not. The other thing I believe we would need to resolve is the Javascript based functionality, which is disabled by default in Druid, requires some work to keep being supported. https://github.com/apache/druid/pull/14795 describes the details I believe, and now that Java 8 has been dropped can probably be re-opened or at least used as a start to resolve this problem. Anyone aware of any additional issues with doing this? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
