Synchronize data from a single Hologres internal table to MaxCompute using a DataWorks synchronization node. This gives you control over field mapping, partition configuration, write mode, and access permissions — and lets you schedule the sync to run automatically on a recurring basis.
What you'll do
Configure the source (Hologres table) and destination (MaxCompute table).
Set field mapping, partition configuration, and write mode.
Configure access permissions for Hologres.
Run and debug the node.
Schedule the node and deploy it to the production environment.
Prerequisites
Before you begin, ensure that you have:
A MaxCompute project and a Hologres instance. See Create a MaxCompute Project and Purchase a Hologres instance.
Both the MaxCompute project and the Hologres instance associated with the workspace as computing resources, with the network connectivity test passed. See Associate a computing resource.
A synchronization node created in a scheduled workflow. See Create a node for a scheduled workflow.
Limitations
Only data in internal databases in Hologres can be synchronized to MaxCompute. External databases are not supported.
For limits on Hologres external tables in MaxCompute, see Hologres external tables.
MaxCompute and Hologres support different data types. Check the type mappings before configuring fields. See Data type mapping between MaxCompute and Hologres.
Configure the synchronization node
Open the configuration tab of the synchronization node and configure the following sections.
Configure the source
| Parameter | Description |
|---|---|
| Source Object Type | Fixed as Hologres Table. |
| Data Source | The Hologres computing resource to read data from. |
| Instance | The Hologres instance ID. Auto-populated and read-only. |
| Database | The Hologres database to read from. |
| Schema | The Hologres schema to read from. |
| Table | The Hologres table to read from. |
| Filter Conditions | A SQL WHERE clause to filter source rows. For partitioned tables, the system generates a default condition automatically. Edit the condition as needed — only rows that match are synchronized. |
A filter condition is the content of the clause after WHERE in an SQL statement.
Configure the destination
| Parameter | Description |
|---|---|
| Data Source | The MaxCompute computing resource to write data to. |
| Project | The MaxCompute project. Auto-populated based on the computing resource. |
| Schema | The MaxCompute schema to store data in. Required only if the schema feature is enabled for your MaxCompute project; hidden otherwise. See Enable the feature. |
| Table | The MaxCompute internal table to write data to. |
| Lifecycle | The retention period for the MaxCompute internal table. If data does not change within this period from the last update time, MaxCompute automatically reclaims the table. |
| Synchronization Fields | The fields to synchronize and their data types in the MaxCompute table. Select fields and configure types as needed. |
| Partition Configurations | The source of data for the partition key column. Field in Hologres uses a specific field from the Hologres table. Scheduling Variable uses a variable defined on the synchronization node. |
Configure data synchronization settings
| Parameter | Description |
|---|---|
| Import Method | How data is written to the destination table. Choose based on your use case: Overwrite deletes all existing data before writing — use this for full refreshes where the destination should always reflect the latest source snapshot. Append keeps existing data and adds new rows — use this for incremental loads or when you need to accumulate historical records. |
| Permissions to Access Hologres | The identity used to access Hologres during synchronization. Dual-signature uses the current identity, which must have read permissions on the MaxCompute table and permissions on the mapped Hologres table. See User guide for Data Lakehouse Solution 2.0 and Permission management overview. RamRole uses a specified RAM role. Attach the AliyunSTSAssumeRoleAccess policy to the role, then set the RoleARN parameter. See RAM role authorization mode. |
| Location | The Hologres external storage path used to generate the MaxCompute table during synchronization. The system auto-generates a path. Customize if needed. |
Run and debug the node
In the right-side navigation pane of the configuration tab, click Run Configuration and set the following parameters.
Parameter Description Computing Resource The MaxCompute computing resource associated with the workspace. Computing Quota The compute quota for this run. Select an existing quota, or click Create Computing Quota in the drop-down list to create one. See Manage compute quotas. Resource Group The resource group that passed the connectivity test when you associated the MaxCompute computing resource with the workspace. CUs for Computing Keep the default value. Script Parameters If your filter condition includes variables in the ${Parameter name}format, set the Parameter Name and Parameter Value here. The node substitutes variables with actual values at runtime. See Configure node scheduling.Click Save, then click Run.
After the debug run succeeds, deploy the node to the production environment to enable scheduled execution.
Troubleshooting
Field type mismatch
If the node fails due to a field type mismatch, check whether the data types of fields in the MaxCompute table are correctly configured. See Data type mapping between MaxCompute and Hologres.
Synchronized data does not match the partition filter
If synchronized data does not match your expected partition, check whether Filter Conditions in the source configuration is correctly set.
What's next
Configure node scheduling: Click Scheduling in the right-side navigation pane and configure the Scheduling Policies section to run the node on a recurring schedule.
Node deployment: Click the
icon in the top toolbar to deploy the node to the production environment. Nodes run on a schedule only after deployment.