Manage global objects to be published - Dataphin - Alibaba Cloud Documentation Center

If the deployment package file that you import changes global objects in the target environment, these objects are listed on the Global Objects page. You can manage or publish these global objects.

Prerequisites

A deployment package file from the source environment has been imported into the target environment. For more information, see Import a deployment package.

Accessing global objects to be published

Log on to Dataphin as a cross-tenant publisher.
On the Dataphin home page, in the top menu bar, choose Management Center > Cross-tenant Publish.
In the navigation pane on the left, choose Migration > Import Deployment Package.
In the Actions column of the target deployment package, click the Publish icon.
Click the Global tab to view the global objects to be published.

View and manage global objects to be published

After you import the deployment package, you can use the Global tab to filter, publish, view details, compare versions, and view version details for objects such as Statistic Period, Global Variable, Calendar, Business Unit, Compute Source, Project, Datasource, Object Attribute, and Feature. The available operations vary by object type.

Operation	Description
Filter	On the Global tab, you can filter all object types. The available filtering methods vary by object type. Batch Search: All object types support batch search. Click Batch Search. In the Batch Search dialog box, enter the search terms for each object. You can enter up to 1,000 terms, separated by line breaks. After you click OK, the system performs an exact search and displays the results in the list. Filter by: Publish Status: The publish status can be To Be Published, In Publish, Publish Successful, Publish Failed, or Succeeded With Warning. Succeeded With Warning means the object was published successfully, but the published content does not exactly match the imported content. This does not affect the use of the published object and only serves as a warning. Change Type: The change types are Add, Update, and Delete. For more information about change types, see Change type description. Environment Change: Indicates whether the target environment has changed since the last import. Compute Source Type: Only Compute Source objects can be filtered by compute source type. The available compute source types are MaxCompute, Blink, Ververica Flink, Hologres, Flink, and FusionInsight Flink. You can select only one compute source type at a time. Data Board: This filter is available only for Project objects. You can select one or more data boards and search for them by entering keywords. Data Source Type: Only Datasource objects can be filtered by data source type and by same name and type. You can select one or more data source types at a time. You can also enter a keyword to search for a data source. For more information about the data sources that Dataphin supports, see Data sources supported by Dataphin. Same Name and Type: Only Datasource objects can be filtered by this criterion. It checks whether the current environment contains a data source with the same name and type as in the source environment. This filter applies only to new data sources. Property Type: Only Object Attribute objects can be filtered by property type and modifier. This includes quality rule attributes. You can select one or more property types at a time. Modifier: Only Object Attribute objects can be filtered by property type and modifier. You can select one or more recent submitters from the system-provided list. Modification Time: Only Object Attribute and Feature objects can be filtered by modification time. You must select a start date and an end date. The date format is YYYY-MM-DD hh:mm:ss.
Publish	You can republish objects that failed to publish or are waiting to be published. You can publish objects individually or in a batch. Successfully published objects do not need to be republished. Single publish: In the Actions column of the target object, click Publish. In the dialog box that appears, enter a name for the publish operation. The name can be up to 64 characters long. Click OK. Note When you publish a single Flink compute source, you must re-enter the compute source information on the Edit Flink Compute Source page. Batch publish: Select the check boxes next to the target objects, or click Select All or Select All on This Page at the bottom of the page. After you select the objects, click Publish at the bottom of the page. In the dialog box that appears, enter a name for the publish operation. The name can be up to 64 characters long. Click OK. Note When you batch publish data sources, data sources with the same name are automatically ignored. Map the data sources or publish them individually first. When you publish data sources, the system verifies their connectivity. If you batch publish multiple data sources and some do not support concurrent operations, the publishing process may be slow. Please wait patiently. Data sources that do not support concurrent operations include SAP Table, HDFS, Hive, Impala, Kudu, Kafka, and other data source types that support Kerberos. Select All applies to all objects that match the current filter and search criteria. Select All on This Page applies only to the objects on the current page. Before you publish a project, make sure that the compute sources on which the project depends are already published. Otherwise, the publish operation fails. Compute Source objects do not support batch publishing.
Publish Details	View the details of a single publish operation, including the Publish Status, the object's Basic Information, the Process Verification results, and any Abnormal Reminders. For Object Attribute and Feature objects, process verification includes Permission Verification, Duplicate Name Verification, and Publish Verification. For all other object types, process verification includes only Publish Verification. Permission Verification: If Permission Verification is set to Verify operator permissions in the cross-tenant publish settings, the system verifies the operation permissions for each object in the target environment during import. If it is set to Ignore permission verification, this check is skipped. Note During the publish process, the system verifies whether the members, after being replaced according to the import policy, have the required operation permissions. Duplicate Name Verification: If the change type for an object attribute is Add or Update, the system checks whether the name of the quality rule attribute is a duplicate. Publish Verification: Verifies whether the publish process is successful. In addition to re-running the preceding pre-checks, the system also performs the following checks: If the change type for an object attribute is Add or Update, it verifies the number of quality rule attributes. If the change type is Delete, it verifies whether the object has already been deleted. Note If the change type of an object is Delete and its publish status is Successful, the object no longer exists in the target environment. In this case, you cannot view its publish details.
Mapping	Supports mapping single or multiple data sources. If data sources with the same name and type exist, you can configure batch mapping. For more information, see Map existing data sources. Note Only Datasource objects support the mapping operation. Data sources with the same name and type can be mapped or renamed before publishing. Data sources with the same name but different types must be renamed before publishing.
Version Details	View the version information of the current data source object, including basic information, production data source, and development data source. Note Only Datasource objects support viewing version details.
Version Comparison	Version comparison is supported only when the change type is Update. It 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 Datasource, Object Attribute, and Feature objects support version comparison.
Set Replacement Rules	Supports setting replacement rules for single or multiple objects. To batch-set data source attributes, you must first set replacement rules. After the rules are set, you can use them to batch publish the data sources. For the steps to set data source replacement rules, see Set data source replacement rules. Note Only Datasource objects support setting replacement rules. Replacement rules are applied when data sources are published. When you publish a single data source, you can choose to enable or disable the replacement rules. To batch-set data source attributes, set the replacement rules first. After the rules are set, you can use them to batch publish the data sources.

Set data source replacement rules

Note

Data source replacement rules can be set only for data source objects.

Attribute configurations often differ between the source and target environments. Before publishing, you can use data source replacement rules to batch replace attribute values from the source configuration. When you publish data source objects, the system applies the first matching rule in sequence to replace the attributes.

Below the list of data source objects, click Set Replacement Rules.

Edit an existing rule or create a new one.

To edit an existing rule: Click the icon in the Actions column for the rule that you want to edit to open the Create Replacement Rule dialog box.
To create a new rule: Click + Create Replacement Rule to open the Create Replacement Rule dialog box.

Configuration Item

Description

Select the scope of data sources to replace

Set the data source type.
Select the type of data source for which you want to replace object attributes. For example, MaxCompute.
Add selection rules.
Click + Add Rule and configure the new rule. If you add multiple rules, they are combined using the AND operator.
Configure the selection scope.
1. Set rule configuration items.
  The available configuration items vary by data source type. For the actual options, refer to the UI. For example, for MaxCompute, you can specify the scope using Datasource Name, Owner, Endpoint, Project Name, and Access ID.
2. Set matching conditions.
  The following matching conditions are supported: Exact Match, Not Match, Contains, Does Not Contain, Starts With, Ends With, Is Empty, Is Not Empty, Empty Text, and Non-empty Text.
  Note
  The matching condition for the Owner attribute is Belongs To.

Set the replacement configuration items and values

Configure replacement items.
The available replacement items vary by data source type. For the actual options, refer to the UI. For example, for MaxCompute, you can replace the Endpoint, Project Name, Access ID, and Access key.
Set matching rules.
Matching rules include Full Text, Text Match, and Regular Expression. The matching is case-sensitive.
Note
Regular expressions follow the Java language specification. For more information, see the Java Regular Expression Tutorial.
Set the replacement text.
Enter the replacement text in the input box.

After you complete the configuration, the rules are applied sequentially.

Click Save.
After you configure the data source replacement rules, the system matches data source objects against the rules and displays the number of matches.
In the Actions column for the desired rule, click the Publish icon to batch publish the data sources that match that rule.
Click to view the data sources that match the rule.
In the Rule Matched Datasources dialog box, you can view the details of the matched data sources, publish them, and map data sources that have the same name and type.

Map existing data sources

Note

You can map only data source objects to existing data sources.

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

Mapping supports two modes: map and update the configuration, or map without modifying the configuration.

Map and update configuration: Maps the imported data source object to the object in the target environment that has the same name and type, and updates the configuration of the target object with the configuration from the imported object.
Note
If a replacement rule is matched, the configuration of the data source is replaced according to the rule.
Map only without modifying configuration: Maps the imported data source object to the object in the target environment that has the same name and type, but does not update the configuration of the target object.