If you want to use Migration Assistant to migrate an object, such as an auto triggered task or a table, you must use the DataWorks export feature to export the object as a package. Then, use the DataWorks import feature to import the package to the desired workspace. This topic describes how to create, view, and manage a DataWorks import task.
Limits
The following table lists the limits on the Migration Assistant service of DataWorks in different editions.
Item
Basic Edition
Standard Edition
Professional Edition
Enterprise Edition
Maximum number of packages that can be exported within a tenant
NoteAfter you create an export task, an export package is generated when the export task succeeds.
If the number of packages that you want to export exceeds the maximum number of packages that can be exported in an edition, you must upgrade the DataWorks edition to meet your business requirements. You cannot pay to export the desired number of packages.
Cumulative quantity: 10
Cumulative quantity: 30
Cumulative quantity: 100
No upper limit
Maximum size of a package that you want to import
On-premises files
30 M
30 M
30 M
30 M
OSS files
Not supported
Not supported
No limit
No limit
Support for automatic commit and deployment during data import
Not supported
Not supported
Supported
Supported
Only an Alibaba Cloud account or a RAM user to which the Workspace Administrator role is assigned can be used to create export or import tasks. If you use a RAM user to which the Workspace Administrator role is not assigned, you can only view export and import tasks.
When you export or import monitoring rules for Data Quality, take note of the following points:
When you export monitoring rules, the alert configurations that are related to the monitoring rules cannot be exported.
If the table that is associated with an imported monitoring rule does not exist in your workspace, the imported monitoring rule is not displayed on the Monitoring Rules page of Data Quality. If you create a table and associate the table with a monitoring rule after the rule is imported, the imported rule is displayed on the rule details page of the table.
If an import package contains monitoring rules and auto triggered nodes, the monitoring rules can be imported only after the auto triggered nodes are imported, committed, and deployed. This way, the auto triggered nodes can be associated with correct monitoring rules.
If an import package contains monitoring rules but does not contain auto triggered nodes, the monitoring rules can be imported. However, the workspace does not contain information about the auto triggered nodes. If an import package contains both the monitoring rules and the auto triggered nodes, the system imports, commits, and deploys the auto triggered nodes, uses the monitoring rules to update the existing monitoring rules, and then associates the auto triggered nodes with the monitoring rules.
Import and export of tasks created in new-version Data Studio are not supported.
Prerequisites
An export task is created.
An export task is created in Migration Assistant to export the object that you want to migrate, such as an auto triggered task or a table. For more information, see Create and view export tasks.
The package that you want to import is prepared.
DataWorks allows you to upload a package from your on-premises machine or Object Storage Service (OSS). You must prepare the package based on the upload method that you select.
Upload from your on-premises machine: Download the package of the export task to your on-premises machine. For more information, see the Create a custom export task section in the "Create and view export tasks" topic.
Upload from OSS: Download the package of the export task to your on-premises machine and store the package in OSS. For more information, see Simple upload.
Go to the Migration Assistant page
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose . On the page that appears, select the desired workspace from the drop-down list and click Go to Data Development.
Click the
icon in the upper-left corner and choose .
Create an import task
In the left-side navigation pane of the Migration Assistant page, choose .
On the Import Task List page, click Create Import Task in the upper-right corner.
In the Create Import Task dialog box, configure the parameters based on your business requirements.
Parameter
Description
Import Package Name
The name of the import task. The name can contain letters, digits, underscores (_), and periods (.).
Upload Method
The source of the package that you want to import. Valid values:
Local Upload: Click Upload File to upload the package from your on-premises machine. The system automatically verifies the package.
NoteThe size of the package cannot exceed 30 MB.
OSS Object: Enter an OSS endpoint in the OSS Endpoint field and click Check. You can log on to the OSS console and perform the steps in the following figure to obtain the URL of the desired package.
After the message The verification succeeded is displayed, you can click Preview File to view the details of the package.
Remarks
The description of the import task.
Click OK. The Import Task Settings page appears.
Make sure that you have checked the format and content of the package before you click OK.
Configure the import task.
When you configure the import task, you must complete the settings in the Computing Resource Mapping section. The following figure provides an example, in which a MaxCompute computing resource is used. The settings in other sections are optional and can be configured based on your business requirements.
NoteIf you migrate data objects between the workspaces that reside in the same region and belong to the same tenant, you need to only configure mappings between compute resources.
In the Computing Resource Mapping section, configure mappings between computing resources in the source workspace to computing resources in the destination workspace.
The Computing Resources in Destination Workspace column displays the display names of the computing resources associated with DataStudio of the destination workspace instead of the project names that are used to create the computing resources. You can go to the DataStudio page and click the
icon in the left-side navigation pane. On the Computing Resource page, you can view the display names of computing resources. If multiple types of computing resources are associated with DataStudio of the source workspace but only one type of computing resource is associated with DataStudio of the destination workspace, the import task fails. This is because the destination workspace does not have creation permissions on the nodes of the remaining types of computing resources.
Optional. In the Resource Group Mapping section, configure a resource group mapping between the source and destination workspaces. This ensures that resource groups are available for imported nodes.
Optional. In the Dependency Mapping section, configure a workspace mapping for the related nodes.
If some tasks to be imported use the name of the source workspace in their code, input parameters, or output names, you must set the New Project Name parameter to the name of the destination workspace. The system uses this name to replace the original workspace name in the code, input parameters, and output names of the tasks. This ensures that the dependencies of the tasks are correct after the tasks are imported.
Optional. In the Dry-run Property section, find the desired node that you want to configure as a dry-run node and click Set to Dry-run in the Actions column.
You can also select multiple nodes and click Batch Set to Dry-run to configure these nodes as dry-run nodes.
This configuration is used to configure time properties for auto triggered nodes. The system returns a success response for the auto triggered node that is configured as a dry-run node without running the node. The node does not generate data.
Optional. In the DataService Studio Settings section, click Specify Mappings for DataService Studio Business Processes.
Optional. In the Committing Rule section, configure the committing rules for resources, functions, and tables, and configure the Change Owner parameter based on your business requirements.
NoteIf the destination workspace contains a data object that has the same name as the data object that you want to import, the data object that you want to import cannot be committed.
If you select Not Modify for the Change Owner parameter and no owner is specified for the node that you want to import, you are automatically configured as the owner of the node after it is imported.
In the lower-left corner of the page, click Start Import.
In the Confirm message, click OK.
View and manage import tasks
On the Import Task List page, the operations that you can perform on import tasks vary based on their status.
After an import task is complete, you can view the details of the task. To view the task details, find the task on the Import Task List page and click View Import Report in the Actions column. On the page that appears, view the task information in the Basic Information, Import Results, Details, and Import Settings sections.
If an import task is in the Editing state, you can perform the following operations on the task:
Modify the task configurations: Click Continue to Edit in the Actions column.
View the task details: Click Preview in the Actions column. On the page that appears, view the task information in the Basic Information, Overview, and Details sections.
Delete the task: Click Delete in the Actions column. In the message that appears, click OK.
If an import task is in the Import Failed state, you can click Import Again in the Actions column of the task. In the Import Progress dialog box, click Return to Import Task List after the import task is complete.