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

Prerequisites

Before publishing a development object, you must first publish its parent domain and project. If they are not published, only metrics are collected, and the object does not appear in the deployment list.
Before publishing a non-SQL compute task with a custom lineage, you must create the referenced tables and fields in the target environment. Otherwise, the deployment will fail.

Note

For a task in Dev-Prod mode, if a referenced table or field exists in the Dev project of the target environment but not in the Prod project, you can still publish the task. However, this creates a risk that the task will be unable to reference the production table or field. Proceed with caution.
If a development object does not appear in the deployment list after you successfully publish its parent domain or project, click Reparse and then refresh the development object list.

Access pending development objects

Log on to Dataphin as a cross-tenant deployment user.
In the top navigation bar of the Dataphin homepage, select Management Center > Cross-tenant Deployment.
In the left-side navigation pane, choose Cross-tenant Deployment > Import Release Package.
In the Actions column for the target release package, click the publish icon.
Click the Development tab to go to the page for development objects to be published.

View and manage pending objects

The objects to be released for the label architecture consist of the node task and offline physical table object types. A node task includes all development objects other than offline physical tables. After a release package is successfully imported, you can perform operations such as filtering, releasing, viewing details, version comparison, and viewing version details for node tasks and offline physical tables on the Development tab. The available actions are slightly different for each object type.

Important

Before managing a development object, ensure that its project is published. If the project is not published, you cannot perform operations such as publishing, viewing details, or version comparison. You also cannot select it for batch operations.

To publish the related data domain, hover over the publish icon in the object's Actions column and click Go to Publish in the tooltip.
If the cross-tenant deployment user is not a member of a published project, you cannot publish objects from that project or perform related operations, including publishing, viewing details, version comparison, and batch operations.

You can hover over the publish icon in the Actions column for the target object and click Go to Join in the tooltip to navigate to the project management page for that project in the current tenant.
After you publish Flink SQL and Flink Stream compute tasks, you must run them manually.

Actions	Description
Filter	You can perform a fuzzy search or batch search by object name. You can also filter `development object`s by project, last submitter, last submission time, object type, `change type`, environment change, or project type. Batch Search: Click Batch Search. In the Batch Search dialog box, enter the supported search terms for each object. You can enter up to 1,000 terms, separated by line breaks. Click OK. The system performs an exact search and lists the matching results. Filter: Project: Select one or more projects to filter by. Deployment status: Select one or more deployment statuses to filter by. Statuses include To Be Published, In Queue, Publishing, Published, Publish Failed, and Succeeded with Risks. `In Queue` means the object is in the deployment queue and awaiting deployment. `Succeeded with Risks` means deployment succeeded, but the deployed content is not identical to the imported content. This does not affect the usability of the deployed object and only serves as a risk alert. Last submitter: Select one or more submitters from the system to filter by. Last submission time: Select a start and end date. The date format is YYYY-MM-DD hh:mm:ss. Object type: You can filter by object type only for `node task` objects. You can select one or more object types. Change type: Select one or more change types to filter by. Change types include New, Updated, and Deleted. Environment change: Select whether the `target environment` has changed since the last import. Project type: Select `Dev-Prod mode` or `Basic mode`.
Publish	You can republish objects with a status of Publish Failed or To Be Published. You do not need to republish objects that have already been published successfully. Both individual and batch publishing are supported. Individual publish: Click Publish in the Actions column for the target object. In the publish dialog box, enter a publish name (up to 64 characters) and click OK. Note When you individually publish an `offline physical table`, if a replacement rule applies to the table, the Publish Confirmation dialog box displays the modified DDL. Batch publish: 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 Publish at the bottom of the page. In the publish dialog box, enter a publish name (up to 64 characters) and click OK. Note Select All applies to all objects that match the current filter and search criteria. Select Current Page applies only to the objects on the current page.
View details	Click the icon to view an object's details. The details shown depend on the object's `change type`. New: Displays the details of the object from the source environment. Updated: Shows a comparison of the object's versions in the source and target environments. Deleted: Displays the details of the object from the `target environment`.
Version comparison	`Version comparison` is available only when the `change type` is Updated. This feature compares the version from the imported `release package` (source) with the latest version in the `target environment`.
Publish details	View the deployment details for a specific publish, including its deployment status, Basic Information, Flow Validation results, and Exception Alerts. Note If an object's `change type` is Deleted and its `deployment status` is Published, the object no longer exists in the `target environment`. In this case, you cannot view its deployment details.
Set replacement rules	Only `offline physical table` objects support replacement rules. Click Set Replacement Rules at the bottom of the page. In the Set Replacement Rules dialog box, you can edit, enable, or disable existing replacement rules, or create new ones. For instructions on how to create a new replacement rule, see Create a replacement rule. Note A replacement rule's scope depends only on the configured Select Replacement Scope for Offline Physical Tables setting, not on which `offline physical table`s you select. If you do not set a scope for a replacement rule, it applies to all `offline physical table`s by default.
Export table creation statements	Only `offline physical table` objects support exporting table creation statements. You can choose to export the statements for multiple tables into a single SQL file or as one SQL file per table. Select the checkboxes next to one or more target objects and click Export table creation statements at the bottom of the page. In the Export table creation statements dialog box, choose an export method and click OK.

Publishing objects

For a project in Dev-Prod mode, the cross-tenant deployment user must have O&M role permissions for the Prod project. For a project in Basic mode, the user must have developer role permissions for the Basic project.

Note

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

Scenario	Development environment	Production environment
All selected objects are in Dev-Prod mode projects, and the user has publishing permissions for all projects.	Supported	Supported
All selected objects are in Dev-Prod mode projects, but the user does not have publishing permissions for all projects.	Supported	Not supported
All selected objects are in Basic mode projects, and the user has publishing permissions for all projects.	Not supported	Supported
All selected objects are in Basic mode projects, but the user does not have publishing permissions for all projects.	Not supported	Not supported
The selected objects belong to a mix of Dev-Prod and Basic mode projects, and the user has publishing permissions for all projects.	Not supported	Supported
The selected objects belong to a mix of Dev-Prod and Basic mode projects, but the user does not have publishing permissions for all projects.	Not supported	Not supported