Manage and publish global objects for cross-tenant publishing after importing a deployment package - Dataphin - Alibaba Cloud - Dataphin

Prerequisites

You have imported a deployment package from the source environment into the target environment. For instructions, see Import a deployment package.

Access global objects

Log on to Dataphin as a cross-tenant deployment user.
On the Dataphin homepage, choose Management Center > Cross-tenant Deployment from the top navigation bar.
In the navigation pane on the left, choose Cross-tenant Deployment > Import deployment package.
In the Operations column for the target deployment package, click the deploy icon.
Click the Global tab to go to the page for global objects pending deployment.

View and manage global objects

On the Global tab, you can filter, deploy, view details, compare versions, and perform other operations on global objects. The available operations vary by object type: Statistics Period, global variable, Public Calendar, Data Board, compute source, project, data source, Object Property, and Identification Feature.

Actions	Description
Filter	You can filter objects on the Global tab by type. The available filter criteria vary by object type. Batch Search: All object types support batch search. Click Batch Search. In the Batch Search dialog box, enter up to 1,000 search terms, with each term on a new line. Click OK. The system performs an exact search and displays the matching objects in the list. Filter: Deployment status: The available statuses are Pending Deployment, Deploying, Deployment Successful, Deployment Failed, and Successful with Risks. Successful with Risks indicates the deployment succeeded but the deployed content does not exactly match the imported content. This status serves as a warning and does not affect usability. Change type: The available change types are Add, Update, and Delete. For descriptions of each change type, see Change Type Descriptions. Environment change: Indicates whether the target environment has changed since the last import. Compute source type: Only objects of the compute source type support filtering by their type. You can select one type at a time, such as MaxCompute, Blink, Ververica Flink, Hologres, Flink, or FusionInsight Flink. Data Board: Only objects of the project type support filtering by data board. You can select one or more data boards by searching for them with keywords. Data source type: Only objects of the data source type support filtering by data source type and by "same name and type". You can select one or more data source types by searching for them with keywords. For a list of data sources supported by Dataphin, see Data sources supported by Dataphin. Same Name and Type: Only objects of the data source type support this filter. This filter applies only to new data sources and finds those that have a counterpart in the target environment with the same name and type. Property type: Only objects of the Object Property type support filtering by property type and modifier. This includes quality rule attributes. You can select one or more property types. Modifier: Only objects of the Object Property type support filtering by modifier. You can select one or more recent modifiers from a system-provided list. Modification time: Only objects of the Object Property and Identification Feature types support filtering by modification time. You must specify a start and end date and time in `YYYY-MM-DD hh:mm:ss` format.
Deploy	You can redeploy failed or pending objects, either individually or in batches. Successfully deployed objects do not need redeployment. Individual deployment: In the Operations column for the target object, click Deploy. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK. Note When you deploy a Flink compute source individually, you must re-enter its information on the edit page. Batch deployment: Select the checkboxes next to the target objects, or click Select All or Select Current Page at the bottom of the page. After selecting the objects, click Deploy. In the dialog box that appears, enter a deployment name (up to 64 characters) and click OK. Note When you deploy data sources in batches, the system automatically ignores those with the same name. You must map them or deploy them individually first. When you deploy a data source, the system checks its connectivity. If you deploy multiple data sources in batches and some of them do not support concurrent operations, the deployment may be slow. Data sources that do not support concurrency include SAP Table, HDFS, Hive, Impala, Kudu, Kafka, and other types that support Kerberos. Select All applies to all objects that match the current filter and search criteria. Select Current Page applies only to objects on the current page. Before deploying a project, ensure that you have already deployed the compute source it depends on. Otherwise, the deployment will fail. compute sources do not support batch deployment.
Deployment details	View deployment details for an individual object, including the deployment status, Basic Information, Process Validation results, and Exception Alert information. For Object Property and Identification Feature objects, Process Validation includes Permission Check, Duplicate Name Check, and Deployment Check. For all other object types, it includes only the Deployment Check. Permission Check: If the cross-tenant deployment settings specify Check Operator Permissions, the system verifies the operator's permissions for each object in the target environment during import. If set to Ignore Permission Check, this step is skipped. Note During deployment, the system checks whether the member has the required permissions after being replaced according to the import policy. Duplicate Name Check: For object properties with a change type of Add or Update, the system checks whether the quality rule attribute name already exists. Deployment Check: Verifies whether the deployment succeeded. In addition to re-running pre-checks, this check verifies the number of quality rule attributes for Add or Update changes, and confirms deletion for Delete changes. Note If an object's change type is Delete and its deployment status is successful, the object no longer exists in the target environment. In this case, you cannot view the deployment details.
Mapping	You can map data sources individually or in batches. If a data source with the same name and type already exists, you can configure batch mapping settings. For instructions, see Map an existing data source. Note Only data source objects support the mapping operation. For data sources with the same name and type, you can either map them or rename one before deployment. For data sources with the same name but different types, you must rename one before you can deploy it.
Version details	View the version information for the current data source object, including Basic Information, Production Data Source, and Development Data Source. Note Only data source objects support viewing version details.
Version comparison	You can compare versions only when the change type is Update. This operation compares the imported object version (from the source environment's deployment package) with the latest version of the corresponding object in the target environment. Note Only data source, Object Property, and Identification Feature objects support version comparison.
Set replacement rule	You can set replacement rules individually or in batches. To set data source properties in batches, you must first define a replacement rule. After you set the rule, you can use it for batch deployments. For instructions, see Set a data source replacement rule. Note Only data source objects support setting replacement rules. The system applies replacement rules during data source deployment. When deploying a single data source, you can choose to enable or disable the replacement rule. To set data source properties in batches, you must first define a replacement rule. After you set the rule, you can use it for batch deployments.

Set a data source replacement rule

Note

Only data source objects support setting data source replacement rules.

Property configurations often differ between source and target environments. You can use replacement rules to automatically replace data source configurations with those required by the target environment before deployment. During deployment, the system applies the first matching rule in the defined order.

Below the list of data source objects, click Set replacement rule.

Edit an existing rule or create a new one.

To edit an existing rule, click the edit icon in the Operations column for the target rule to open the New Replacement Rule dialog box.
To create a new rule, click +New Replacement Rule to open the New Replacement Rule dialog box.

Parameter

Description

Select the scope of data sources to replace

Set data source type.

Select the type of data source whose properties you want to replace, such as MaxCompute.
Add scoping rules.

Click +Add Rule and configure your replacement rule. The rules are combined using a logical AND.
Configure the scope.
1. Set the rule configuration items.
  
  The available configuration items vary by data source type. For example, a MaxCompute data source supports scoping by Data source name, Owner, Endpoint, Project name, and Access ID.
2. Set the match condition.
  
  The available conditions include Exact Match, Does not Match, Contains, Does not Contain, Starts With, Ends With, Is Empty, Is Not Empty, Empty String, and Non-empty String.
  
  Note
  For the Owner field, only the Belongs to condition is supported.

Set replacement items and values

Configure the replacement items for the production and development environments.

The available replacement items vary by data source type. For example, a MaxCompute data source supports replacing Endpoint, Project name, Access ID, and Access key.
Set the match rule.

Match rules include full text, text matching, and regular expression. The match is case-sensitive.

Note
Regular expressions follow Java's syntax. For more information, see the Java regular expression guide.
Set the replacement text.

Enter the text to use as the replacement.

After configuration, the system applies the rules to perform the replacements.

Click Save.

After you configure the data source replacement rule, the system matches the rule to data source objects and displays the number of matches found.

In the Operations column for the target rule, click the deploy icon to deploy the data sources in a batch according to the rule.
Click to view the data sources that match the rule.

In the Data sources matching rule dialog box, you can view details of the matching data sources, deploy them, and perform mapping operations for data sources that have the same name and type.

Map an existing data source

Note

Only data source objects can be mapped to an existing data source.

If an imported deployment package contains a data source with the same name and type as one in the target environment, you can configure a mapping. In the Map existing data source dialog box, click View Details for Comparison to compare the imported data source with the existing one.

You can choose to map and update the configuration, or to map without modifying the configuration.

Map and update configuration: Maps the imported data source object to the existing data source in the target environment and updates the target's configuration with the imported configuration.

Note
If a replacement rule is matched, the system replaces the data source's configuration according to that rule.
Map only, do not modify configuration: Maps the imported data source object to the existing data source in the target environment but does not update the target's configuration.

Multi-engine deployment

In multi-engine mode, if the compute source uses independent configuration, it can be deployed directly even when the target tenant does not support this mode. If the compute source uses reference cluster mode but no corresponding cluster exists in the target tenant, click the configuration cluster link to go to the cluster management page and create the required cluster.