Manage development objects pending release-Dataphin(Dataphin)-阿里云帮助中心

If an imported deployment package contains development objects, they appear on the development objects pending release page, where you can manage and release them.

Prerequisites

The business segment and project that contain the development object must be published. If they are not published, the system only collects metrics and no corresponding object appears in the release list.
For non-SQL compute nodes with custom lineage, create the tables and fields required for the node's lineage in the target environment before you publish. This prevents publishing errors.

Note

If a Dev-Prod node references tables and fields that exist in the Dev project of the target environment but not in the Prod project, you can still publish the node. However, this carries a risk that references to the production tables and fields may fail. Proceed with caution.
If the corresponding object does not appear in the release list after the business segment or project is successfully published, click Reparse. Then, refresh the development object list.

Entry point for development objects pending release

Log in to Dataphin using a cross-tenant publishing user account.
On the Dataphin homepage, choose Management Center > Migration from the top menu bar.
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 Development tab to open the development objects pending release page.

View and manage development objects pending release

Development objects pending release for the tag architecture consist of two object types: Node Tasks and Offline Physical Tables. Node Tasks include all development objects except for offline physical tables. After you import a deployment package, go to the Development tab. You can then filter, publish, view details, compare versions, and view version details for Node Tasks and Offline Physical Tables. The available operations differ slightly between object types.

Important

Before you manage any development object, ensure that the related project is published. If the project is not published, you cannot perform operations such as publishing, viewing details, or comparing versions. You also cannot select the objects for batch operations.
You can publish the project by hovering over the publish icon in the Actions column of the target data architecture object and clicking Publish in the tooltip that appears.
For objects in published projects, if the cross-tenant publishing user is not a member of the project, that user does not have permission to publish the object. That user also cannot perform related operations such as publishing, viewing details, comparing versions, or batch operations.
You can hover over the Publish icon in the Actions column of the target data architecture object to be published and click Join in the tooltip to open the project management page for this project within the current tenant.
After you publish Flink SQL and Flink Stream compute nodes, you must run them manually.

Operation	Description
Filter	You can perform a fuzzy search or batch search by object name. You can also filter development objects by project, recent submitter, recent submission time, object type, change type, environment change, or project type. Batch Search: Click Batch Search. In the Batch Search dialog box, enter the search terms supported by each object. You can enter up to 1,000 terms, separated by carriage returns. Click OK. The system performs an exact search and displays the results in the list. Filter: Project: Select one or more projects to filter by. Release Status: Select one or more release statuses to filter by. Statuses include Pending Release, Releasing, Release Successful, Release Failed, and Successful with Risks. Successful with Risks means the object was published successfully, but the published content is not identical to the imported content. This status indicates a risk but does not affect the use of the object. Recent Submitter: Select one or more recent submitters to filter by. The list of submitters is sourced from the system. Recent Submission Time: Select a start date and an end date. The date format is YYYY-MM-DD hh:mm:ss. Object Type: Only node tasks support filtering by object type. You can select one or more object types. Change Type: Select one or more change types to filter by. Change types include Add, Update, and Delete. Environment Change: Select whether the target environment has changed since the last import. Project Type: Select Dev-Prod or Basic mode.
Publish	You can republish objects that failed to publish or are pending publication. Both single and batch publishing are supported. Successfully published objects do not need to be republished. Single publish: Click Publish in the Actions column for the target object. In the dialog box that appears, enter a release name of up to 64 characters and click OK. Note When you publish a single offline physical table, if the table matches an active replacement rule, the confirmation dialog box for the release displays the DDL statement after replacement. 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. In the dialog box that appears, enter a release name of up to 64 characters and click OK. Note 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.
View details	Click to view the details of the object. The details shown vary based on the change type. Add: Displays the details of the object from the source environment. Update: Displays a comparison between the source and target environments. Delete: Displays the details of the object from the target environment.
Version comparison	Version comparison is supported only when the change type is Update. This operation compares the version of the object in the current import (from the source environment's deployment package) with the latest version of the corresponding object in the target environment.
Release details	View the details of a single release. The details include the Release Status, the object's Basic Information, Flow Check results, and Exception Alerts. Note If the change type of an object is Delete and its release status is Successful, the object no longer exists in the target environment. In this case, you cannot view the release details.
Set replacement rules	Only objects of the offline physical table type support replacement rules. Click Set Replacement Rules at the bottom of the page. In the Set Replacement Rules dialog box, select existing rules to edit, enable, or disable them. You can also create new replacement rules. For more information about how to create a new replacement rule, see Create a new replacement rule. Note The scope of a replacement rule depends only on the configured Scope of offline physical tables to replace. It is not related to the offline physical tables you select on this page. If no scope is set for a replacement rule, the rule applies to all offline physical tables by default.
Export table creation statements	Only objects of the offline physical table type support exporting table creation statements. You can export the statements for multiple tables into a single SQL file or generate a separate SQL file for each table. Select the check boxes for one or more target objects. Click Export Table Creation Statements at the bottom of the page. In the Export Table Creation Statements dialog box, select an export method and click OK.

Release object description

For projects in Dev-Prod mode, the cross-tenant publisher must have the O&M role for the Prod project. For projects in Basic mode, the cross-tenant publisher must have the Developer role for the Basic project.

Note

Publishing to production means publishing to the Prod or Basic environment. Publishing to development means publishing to the Dev environment. Basic mode does not support publishing to the development environment.

Scenario description	Development environment	Production environment
All projects for the release objects are in Dev-Prod mode, and the user has publishing permissions for all projects.	Supported	Supported
All projects for the release objects are in Dev-Prod mode, but the user does not have publishing permissions for all projects.	Supported	Not supported
All projects for the selected objects are in Basic mode, and the user has publishing permissions for all projects.	Not supported	Supported
All projects for the selected objects are in Basic mode, but the user does not have publishing permissions for all projects.	Not supported	Not supported
The projects for the selected objects include both Dev-Prod and Basic mode projects, and the user has publishing permissions for all projects.	Not supported	Supported
The projects for the selected objects include both Dev-Prod and Basic mode projects, but the user does not have publishing permissions for all projects.	Not supported	Not supported

上一篇: Manage data architecture objects to be published 下一篇: Managing label schema objects to be published