Clarification on Default Socket Timeout Behavior Introduced in v2.6.35

Data Engineering

Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.

Hi Team,

I’m currently using the Databricks JDBC driver version 2.6.40, and I’ve noticed intermittent socket timeout errors during pipeline execution.

I came across the release note for version 2.6.35 mentioning the following change:

[SPARKJ-688] The connector turns on the socket timeout by default for HTTP connections and provides default values.

Could you please confirm:

What is the default socket timeout value that was introduced in version 2.6.35?
Based on the intermittent timeouts I’m encountering, would increasing the SocketTimeout value in the JDBC URL help mitigate this issue?

Thanks,

Balram