Help Center/ DataArts Studio/ User Guide/ DataArts Migration (Offline Jobs)/ Configuring Connection Properties/ Configuring MySQL Connection Properties
Updated on 2026-05-20 GMT+08:00
View PDF
Share

Configuring MySQL Connection Properties

When using DataArts Migration, you can configure properties of the JDBC connection to the MySQL data source to optimize the data migration process and resolve possible problems.

This section describes the connection properties. You can add JDBC properties of the connection to a specified data source and configure the properties by referring to the JDBC connector documentation of the corresponding database.

Optional Connection Properties

Property

Type

Description

connectTimeout

int (unit: ms)

Connection timeout interval. When a large amount of data needs to be migrated or the entire table is retrieved using query statements, the migration may fail due to connection timeout. To prevent such failures, you can customize the connection timeout interval. Example: connectTimeout=360000.

socketTimeout

int (unit: ms)

Socket timeout interval. When a large amount of data needs to be migrated or the entire table is retrieved using query statements, the migration may fail due to socket timeout. To prevent such failures, you can customize the socket timeout interval. Example: socketTimeout=360000.

tinyInt1isBit

boolean

By default, tinyInt1isBit is set to true. In this case, TINYINT(1) is processed as BIT (Types.BOOLEAN), and 1 or 0 is read as true or false, which will cause a migration failure. You can disable this configuration to avoid migration errors, that is, set tinyInt1isBit to false.

mysql.bool.type.transform

boolean

Controls the processing mode of TINYINT(1), which is similar to tinyInt1isBit. When tinyInt1isBit is set to false, this parameter can further ensure that Boolean data is correctly processed. Example: mysql.bool.type.transform=false.

useCursorFetch

boolean

By default, useCursorFetch is set to true, indicating that the JDBC connector communicates with relational databases through a binary protocol. Some third-party systems may have compatibility issues, causing migration time conversion errors. In this case, you can disable this function. The open-source PostgreSQL database supports the useCursorFetch parameter. You do not need to set this parameter. Example: useCursorFetch=false.

allowPublicKeyRetrieval

boolean

The public key retrieval mechanism is disabled by default in PostgreSQL. If TLS is unavailable and the RSA public key is used for encryption, an error may occur for a connection to a PostgreSQL data source. To prevent such an error, you can enable public key retrieval. Example: allowPublicKeyRetrieval=true.

Configuration Method

  1. On the Management Center page, locate the MySQL data source configuration.
  2. In the connection property configuration area, click Add to add properties for the connection.
  3. Enter property names and values as needed based on the descriptions in the preceding table.
  4. Save the change and test the connection to ensure that the configuration takes effect and data can be migrated properly.

Precautions

  • When configuring connection properties, ensure that you understand the meaning and function of each property to avoid data migration failures or other issues due to incorrect configurations.
  • If you have any questions during the configuration, refer to the official MySQL JDBC connector documentation for more information and instructions.
  • You are advised to adjust and optimize connection properties based on the data migration scenarios and requirements to achieve optimal migration performance.

By properly configuring MySQL connection properties, you can improve data migration stability and efficiency for smooth data integration.