topic Re: Databricks JDBC Driver Version 42 Limitations in Data Engineering

Databricks JDBC Driver Version 42 Limitations

Ankit_Kothiya — Thu, 22 May 2025 12:35:51 GMT

We found that the Databricks JDBC driver does not support:

Connection.setAutoCommit(false)
Connection.commit()
Connection.rollback()
Execution of BEGIN TRANSACTION

Can you help us understand why these operations are not supported by the Databricks JDBC driver?
Is there an alternative JDBC driver for Databricks that supports the above-mentioned operations?

Re: Databricks JDBC Driver Version 42 Limitations

SP_6721 — Fri, 23 May 2025 15:06:44 GMT

Hi @Ankit_Kothiya

As far as I know, the Databricks JDBC driver doesn’t support manual transaction controls like setAutoCommit(false), commit(), rollback(), or BEGIN TRANSACTION. That’s because Delta Lake are designed to support atomic operations at the single statement or table level, not multi-statement transactions like you’d find in traditional databases. The JDBC driver runs in auto-commit mode by default, so it doesn’t allow for manual transaction handling.
As of now, there isn’t another JDBC driver for Databricks that supports those manual transaction features. Instead, you can use operations like MERGE or INSERT OVERWRITE, which are atomic on their own. And if you ever need to roll back changes, Delta Lake’s Time Travel feature can help with that.

Re: Databricks JDBC Driver Version 42 Limitations

Ankit_Kothiya — Mon, 26 May 2025 18:03:35 GMT

Thank you, @SP_6721 , for your input!

Could you please share an example snippet demonstrating how to handle batch processing, similar to what we typically do in a relational database?