jnturton commented on issue #2882: URL: https://github.com/apache/drill/issues/2882#issuecomment-1965733063
Hi. To this day, every binary distribution of Drill released by the project, including the published Maven artifacts, maintains JDK 8 compatibility. Even when that distro is bundled with a newer JDK, e.g. the Docker image based on JDK 17. > We are using maven as a build system and have org.apache.drill.exec:drill-jdbc:jar:1.21.0 as a dependency @Der-Joscha, please use the artifact org.apache.drill.exec:drill-jdbc-all:jar:1.21.0 instead, this is the JDBC driver repackaged for distribution. > Drill is tested against Java 8, 11, and 17. I had always assumed the same is true of Drill's JDBC driver, but it seems now that might not be the case? It is the case. The _repackaged_ driver, jdbc-all, is [only minimally tested](https://github.com/apache/drill/actions/runs/7780452805/job/21213166830#step:5:24009) but I, for one, use it locally under Java 17. > Do you know whether the JDBC driver gets updated in mvncentral when we do updates? It does, [here are the artifacts for 1.21.1](https://repository.apache.org/content/repositories/releases/org/apache/drill/exec/drill-jdbc-all/1.21.1/). @Der-Joscha let us know if the module access errors are resolved when you switch to jdbc-all. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@drill.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
