DQ&C 16.3.1 Upgrade Notes

Connection-timeout-property for JDBC drivers

All JDBC data source drivers now require the connection-timeout-property setting.

The property specifies the driver-level property name and unit used to enforce a socket or read timeout on JDBC connections. If it is missing, Data Processing Engine (DPE) can become completely blocked when a data source is unresponsive.

The property follows this pattern:

plugin.jdbcdatasource.ataccama.one.driver.<driverId>.connection-timeout-property = <property>, <unit>

Where

<property> is the JDBC driver property name.
<unit> is s (seconds) or ms (milliseconds).

Set the value to NONE for drivers that do not support a timeout property.

When upgrading to 16.3.1, verify that each configured driver (default or custom) includes connection-timeout-property.

Reference values for default drivers

For full configuration details, see Data Sources Configuration.

Driver Value

Driver	Value
Amazon Aurora MySQL	`socketTimeout, ms`
Amazon Aurora PostgreSQL	`socketTimeout, s`
Amazon Redshift	`socketTimeout, s`
Apache Cassandra	`ReadTimeoutMillis, ms`
Arrow Flight SQL (Dremio)	`socketTimeout, ms`
AWS Athena	`SocketTimeout, s`
Azure Data Explorer (ADX)	`socketTimeout, ms`
Azure Synapse Analytics	`socketTimeout, ms`
BigQuery	`Timeout, s`
IBM Db2	`blockingReadConnectionTimeout, s`
IBM Netezza	`loginTimeout, s`
Informix	`INFORMIXCONTIME, s`
MariaDB	`socketTimeout, ms`
MS SQL	`socketTimeout, ms`
MySQL	`socketTimeout, ms`
Oracle	`oracle.jdbc.ReadTimeout, ms`
PostgreSQL	`socketTimeout, s`
SAP HANA	`webSocketPingTimeout, s`
Snowflake	`loginTimeout, s`
SQLite	`NONE`
Sybase	`com.sybase.CORBA.socketTimeout, s`
Teradata	`NONE`

Amazon Aurora MySQL

socketTimeout, ms

Amazon Aurora PostgreSQL

socketTimeout, s

Amazon Redshift

socketTimeout, s

Apache Cassandra

ReadTimeoutMillis, ms

Arrow Flight SQL (Dremio)

socketTimeout, ms

AWS Athena

SocketTimeout, s

Azure Data Explorer (ADX)

socketTimeout, ms

Azure Synapse Analytics

socketTimeout, ms

BigQuery

Timeout, s

IBM Db2

blockingReadConnectionTimeout, s

IBM Netezza

loginTimeout, s

Informix

INFORMIXCONTIME, s

MariaDB

socketTimeout, ms

MS SQL

socketTimeout, ms

MySQL

socketTimeout, ms

Oracle

oracle.jdbc.ReadTimeout, ms

PostgreSQL

socketTimeout, s

SAP HANA

webSocketPingTimeout, s

Snowflake

loginTimeout, s

SQLite

NONE

Sybase

com.sybase.CORBA.socketTimeout, s

Teradata

NONE

Databricks JDBC batch inserts

Starting with Simba 2.6.38 and OSS 3.0.5, the JDBC Writer inserts records one at a time, causing slow writes. Ataccama ONE now automatically restores batched inserts for Simba 2.7.0+ and OSS 3.0.5+.

If you are using Simba 2.6.38–2.6.x, manually add ;EnableNativeParameterizedQuery=0 to your connection string.

For details, see Slow write operations on Databricks JDBC connections.

Was this page useful?