Configure real-time full-database synchronization tasks

Step 4: Advanced Configuration > DDL capability configuration — New paragraph: Delete column limitation

Location: After the following sentence in the DDL capability configuration section: "After a column is added to the source table and created in the destination table via DDL sync, the system does not backfill the existing data in the destination table."

Current content:

(No content about delete column limitations currently exists in this section.)

New content:

Column deletion is not supported for automatic synchronization in MySQL sources. When you delete a column from a source MySQL table, the table schema becomes inconsistent with the binary log, which may cause synchronization task errors.

To remove a field that has already been synchronized to the destination table, use the following workaround:

1. Delete the corresponding destination table (for example, the Hologres destination table).

2. Edit the synchronization task and remove the table from the task.

3. Re-add the table to the task.

4. Click Refresh to update the field mappings.

5. Save and publish the task.

6. If the task is in the running state, click Apply Updates for the changes to take effect.

These steps rebuild the table mapping to reflect the updated source table schema.

Step 3: Synchronization plan configuration > 3. Target table mapping — New paragraph: MaxCompute target schema name mapping

Location: In the 3. Target table mapping section, after the target table name mapping customization description area.

Current content:

(No content describes MaxCompute target schema name mapping support in this area.)

New content:

In real-time full-database synchronization tasks, MaxCompute also supports target schema name mapping customization. You can configure custom schema name mapping rules to route synchronized data to a specified non-default schema in the destination MaxCompute project, rather than writing all data to the default schema.