JDBC driver uses Unsafe API, which will be completely deprecated in a future release of Java

benesq — Mon, 23 Jun 2025 19:09:06 GMT

Using JDBC driver (2.7.3) in OpenJDK 24 gives the following warning:

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called WARNING: sun.misc.Unsafe::arrayBaseOffset has been called by com.databricks.client.jdbc42.internal.apache.arrow.memory.util.MemoryUtil WARNING: Please consider reporting this to the maintainers of class com.databricks.client.jdbc42.internal.apache.arrow.memory.util.MemoryUtil WARNING: sun.misc.Unsafe::arrayBaseOffset will be removed in a future release

While it's uncertain what Java release it will be deprecated in, I think this needs to be fixed sooner rather than later. Java's new FFM API provides a nice way of handling Off-Heap memory and probably would fix whatever this MemoryUtil class is trying to do in a safe way. There are also other alternatives.

Thanks,

Ben

Re: JDBC driver uses Unsafe API, which will be completely deprecated in a future release of Java

NandiniN — Sat, 04 Oct 2025 04:37:00 GMT

Hey @benesq ,

For JDBC driver 2.7.4 https://www.databricks.com/spark/jdbc-drivers-download should be used with

Java Runtime Environment (JRE) 8.0, 11.0 or 21.0. As mentioned in the installation doc "Each machine where you use the Databricks JDBC Driver must have Java Runtime Environment (JRE) 8.0, 11.0 or 21.0."

This will be fixed in a subsequent version of JavaFX side, https://bugs.openjdk.org/browse/JDK-8345121 does mention the issue is now resolved.

Thanks!

topic JDBC driver uses Unsafe API, which will be completely deprecated in a future release of Java in Data Engineering

JDBC driver uses Unsafe API, which will be completely deprecated in a future release of Java

Re: JDBC driver uses Unsafe API, which will be completely deprecated in a future release of Java