Version updates - MaxCompute - Alibaba Cloud Documentation Center

This topic describes the latest version updates of Java Database Connectivity (JDBC), including new and enhanced features of a specific version of JDBC.

The following table describes the latest version updates of JDBC. For more information, visit the URL of the related version or Github Release Note.

Version	Change type	Description
v3.8.8	New feature	The `skipCheckIfSelect` parameter is supported, allowing users to skip the SQL parsing capability introduced in JDBC 3.4.1. Note When this parameter is set to True, the SQL parsing feature introduced in JDBC 3.4.1 will not be used.
v3.8.5	New feature	MaxQA is supported.
v3.4.3	New feature	The timeout period can be configured in MaxCompute tunnels.
v3.4.2	Enhanced feature	The SDK is updated. Prepared statements can be executed in the MaxCompute V2.0 data type edition.
v3.4.1	Fixed issue	SDK-related issues are fixed.
v3.4.1	New feature	The automatic rollback feature is supported in MaxCompute Query Acceleration (MCQA) mode. If you submit an SQL statement that is not supported by MCQA in an MCQA job, the MCQA job can be automatically rolled back to an SQL query job. SQL statements such as UPDATE, DROP, CREATE, and ALTER are not supported by MCQA. Note This feature relies on the SQL parsing capability introduced in this version (using Antlr4), which consumes more CPU and memory resources compared to previous versions. The resource consumption amount is proportional to the SQL complexity. We recommend that you pay attention to resource usage and manage concurrency when executing complex queries. Alternatively, you can upgrade to JDBC 3.8.8 or JDBC 3.9.3, and configure `skipCheckIfSelect=true` to bypass this SQL parsing functionality.
v3.3.4	Fixed issue	Time zone-related issues are fixed. Log-related issues are fixed.
v3.3.2	Fixed issue	Time zone-related issues are fixed. The following issue is fixed: A three-layer model can be configured at the tenant level when a project does not support the three-layer model.
v3.3.0	New feature	A three-layer model is supported.
v3.2.29	Fixed issue	The issue that is related to the configuration of the autoSelectLimit parameter is fixed.
v3.2.28	New feature	The `getLogview` and `getInstance` operations are added.
v3.2.26	Fixed issue	Known issues are fixed.
v3.2.25	Fixed issue	The issue that is related to the Fallback service is fixed.
v3.2.9	New feature	The connection string parameter `useProjectTimeZone` is added. This parameter is optional. Default value: False. If you configure `useProjectTimeZone=true`, the return values of `ResultSet#getDate`, `ResultSet#getTime`, and `ResultSet#getTimestamp` are determined based on the time zone where the current project resides.
	Enhanced feature	The logs that record job failures are optimized.
	Fixed issue	The Maven AspectJ plug-in cannot be used. This avoids possible performance losses.
v3.2.8	New feature	The MaxCompute Query Acceleration (MCQA) feature is supported.
v3.2.8	Enhanced feature	In MCQA mode, you can add the option `instanceTunnelMaxRecord` to specify the maximum number of rows of results that can be read. The default value is -1, which indicates the number of rows of results that can be read is not limited. This option is supported only for JDBC 3.2.7 or later. In MCQA mode, you can add the option `instanceTunnelMaxSize` to specify the maximum size of data that can be read in bytes. The default value is -1, which indicates the size of data that can be read is not limited. This option is supported only for JDBC 3.2.7 or later. In MCQA mode, you can add the option `disableConnectionSetting` to disable settings for connections. If you add the option `alwaysFallback` and set the option to True in MCQA mode, the query jobs in MCQA mode are rolled back to the offline mode in the preceding scenarios. This option is supported only for JDBC 3.2.3 or later.