MaxCompute:Version updates

v3.8.8

New feature

• Added the skipCheckIfSelect parameter. When set to true, the SQL parsing introduced in v3.4.1 is skipped.

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

• Added support for MaxQA.

v3.4.3

New feature

• The timeout period for MaxCompute tunnels is now configurable.

v3.4.2

Enhancements

• Updated the SDK.

• Prepared statements can now be executed in the MaxCompute V2.0 data type edition.

v3.4.1

New feature

• Added automatic rollback in MaxCompute Query Acceleration (MCQA) mode. If an SQL statement not supported by MCQA — such as UPDATE, DROP, CREATE, or ALTER — is submitted in an MCQA job, the job automatically falls back to a standard SQL query job.

  This feature relies on SQL parsing powered by ANTLR4, which uses more CPU and memory than previous versions. Resource consumption scales with query complexity. Monitor resource usage and manage concurrency when running complex queries. To skip this SQL parsing without downgrading, upgrade to v3.8.8 or v3.9.3 and set skipCheckIfSelect=true.

Bug fix

• Fixed SDK-related issues.

v3.3.4

Bug fixes

• Fixed time zone-related issues.

• Fixed log-related issues.

v3.3.2

Bug fixes

• Fixed time zone-related issues.

• Fixed an issue where the three-layer model could be configured at the tenant level even when the project did not support it.

v3.3.0

New feature

• Added support for the three-layer model.

v3.2.29

Bug fix

• Fixed an issue with the configuration of the autoSelectLimit parameter.

v3.2.28

New features

• Added the getLogview and getInstance operations.

v3.2.26

Bug fix

• Fixed known issues.

v3.2.25

Bug fix

• Fixed an issue with the Fallback service.

v3.2.9

New feature

• Added the optional connection string parameter useProjectTimeZone. Default: false. When set to true, the return values of ResultSet#getDate, ResultSet#getTime, and ResultSet#getTimestamp are based on the time zone of the current project.

Enhancement

• Improved job failure logs.

Bug fix

• The Maven AspectJ plug-in cannot be used. This avoids possible performance losses.

v3.2.8

New feature

• Added support for MaxCompute Query Acceleration (MCQA).

Enhancements

• Added the instanceTunnelMaxRecord option for MCQA mode. Specifies the maximum number of rows readable per query. Default: -1 (unlimited). Requires JDBC 3.2.7 or later.

• Added the instanceTunnelMaxSize option for MCQA mode. Specifies the maximum amount of data readable, in bytes. Default: -1 (unlimited). Requires JDBC 3.2.7 or later.

• Added the disableConnectionSetting option for MCQA mode. When set, connection-level settings are disabled.

• Added the alwaysFallback option for MCQA mode. When set to true, MCQA query jobs automatically fall back to offline mode. Requires JDBC 3.2.3 or later.