Incremental release packages are ideal for exporting project results in phases, such as changes within a specific timeframe or objects from a particular business segment or project. This topic describes the process for incrementally exporting release package files from the source environment.
Prerequisites
In the cross-tenant release settings, configure the credentials for release, storage location for the deployment package, permission verification, and approval processes. For more information, see cross-tenant release settings.
The source environment has transitioned to maintenance mode for the cross-tenant release. For detailed instructions, see maintain/upgrade Dataphin.
Permission description
Users with cross-tenant release permissions can incrementally export release package files.
Procedure
Log on to Dataphin with the cross-tenant release user account.
In the top menu bar of the Dataphin homepage, select Management Hub > Migration.
In the left-side navigation pane, select Migration > Export Release Package.
On the Export Release Package page, click New Release Package.
On the New Release Package page, configure the parameters.
Select Export Method as Incremental Export. The other parameters in the Basic Information and Export Information sections are configured the same way as for full export release packages. For more information, see full export release packages.
Click Save And Next.
In the Export Scope step, configure the export scope for objects.
Parameter
Description
Last Change Date
Supports both All Dates and Specified Dates options.
NoteObjects with a Last Change Date outside the selected date range will be excluded from the filter results, regardless of any changes that occurred within that range.
Object Type
Select the required object type for export. Supported types include Global, Data Architecture, Development, Tag Architecture, Tag, Standard, Data Quality, Data Security object types.
Global: Encompasses statistical period, global variables, public calendars, offline scheduling templates, data segments, compute sources, projects, data sources, object attributes, and detection features.
Data Architecture: Covers subject domains, business objects, and business activities.
Development: Includes offline pipelines, logical fact tables, logical dimension tables, business filters, atomic metrics, derived metrics, logical aggregate tables, resources, functions, compute tasks (support for different compute tasks varies by compute engine), database SQL, SHELL, PYTHON, VIRTUAL, meta tables, image tables, offline computing templates, and trigger nodes.
Tag Architecture: Comprises entities and entity IDs.
Tag: Includes offline datasets, offline tags, and behavior relationships.
Standard: Consists of lookup table directories, data standard set directories, public standard attributes, standard templates, data standard sets, data standards, mapping rules, mapping relationships, lookup tables, and root words.
Data Quality: Includes rule templates and quality rules.
Data Security: Encompasses data classification, data grading, detection features, detection results, and keys.
Data Segments And Projects
Choose the data segments and projects for the objects you want to export. The security detection results will be exported according to the selected data segments and projects. Note that when filtering resources related to development, the data sources and quality remain unaffected by the filter criteria.
ImportantSelecting a Project is a mandatory option, otherwise you might not be able to retrieve the export objects.
Click Export Release Package to complete the incremental export package settings.
Click Save Release Package to generate a draft record on the release package list page, which you can then edit.
Click Save And Preview to generate a draft record on the release package list page and automatically navigate to the export content preview page. You can view the export configuration and export details of the release package. Click the Return To Edit button at the bottom or the Edit button next to the basic information/export information to return to the release package edit page.
The export time varies depending on the volume of data being exported and may take from several minutes to a few hours.