Dataphin:Export a full release package

Prerequisites

• Deployment credentials, storage location, permission checks, and approval settings are configured in the cross-tenant deployment settings. For more information, see Cross-tenant deployment settings.

• The source environment must be in maintenance mode for cross-tenant deployment. For instructions, see Maintain/Upgrade Dataphin.

Permissions

Only users with cross-tenant deployment permissions can export a full release package.

Procedure

1. Log on to Dataphin using an account with cross-tenant deployment permissions.

2. In the top navigation bar of the Dataphin homepage, choose Management Center > Cross-tenant Deployment.

3. In the left-side navigation pane, choose Cross-tenant Deployment > Export Release Package.

4. On the Export Release Package page, click Create Release Package.

5. On the Create Release Package page, configure the parameters.

   Parameter		Description
   Basic information	Release package name	The system generates a default package name that you can modify. The file name format is TenantName_CreationTime.dp. The destination environment accepts only release packages in .dp format. The package name cannot start with a period (.) or a space. A release package name cannot contain the following characters: question mark (?), enumeration comma (、), forward slash (/), backslash (\), double quotation marks ("), angle brackets (<>), vertical bar (|), or colon (:).  The name can be up to 255 characters long. Each Chinese character counts as two characters.
   	Release package description	Enter a description for the release package, up to 64 characters long.
   Export information	Export object settings	Export method: Select Full Export. Table creation statements: You can choose to Export or Not export table creation statements. If you choose to export them, the system queries engine metadata, which may take a long time depending on the engine's performance.
   	Compute engine export settings	Connection information: The default is Retain. You can also select Clear. Authentication information: The default is Clear. You can also select Retain. Warning Retaining authentication information includes it in the release package. Handle the package file securely and avoid sharing it.
   	Data source export settings	Connection information: The default is Retain. You can also select Clear. Authentication information: The default is Clear. You can also select Retain. Warning Retaining authentication information includes it in the release package. Handle the package file securely and avoid sharing it.
   	Data standard export settings	If the data standard feature is enabled, you can filter the mappings exported from the source environment. Export only manually added mappings: Exports mappings with manually added details, including those imported from Excel or associated during development. All mappings: Exports all mappings from the source environment.
   	Data security export settings	If the data security feature is enabled, you can filter the key values and security identification results exported from the source environment. Key value: You can choose to export or not export key values. Export: Key values are exported from the source environment and can be deployed immediately after being imported into the destination environment. Do not export: Exports the name and type of the key, but not the key value itself. You must regenerate or enter the key value in the destination environment after import. Note Key values are sensitive data. The system transmits them as ciphertext during export and decrypts them after import. Security identification results: You can export only manually specified results or all identification results. Export only manually specified results: Exports manually specified identification results from the production environment. This includes results uploaded in bulk from Excel and those added manually. All identification results: Exports all identification results from the source environment's production environment.
   	Transfer settings	If OSS Storage is enabled in the cross-tenant deployment settings, the Export File page displays transfer settings. The exported release package is automatically stored in the specified OSS location. Automatically transfer to external storage upon completion: Disabled by default. Select this option to automatically save the release package to the specified OSS location after export. Duplicate file handling: Supports Rename, Ignore, and Overwrite. Rename: Automatically renames the release package file. If a file with the same name exists, the system appends 'Copy N' to the new filename. If a file named 'Copy N' already exists, the number is incremented to N+1. Ignore: Skips the current transfer operation. Overwrite: Overwrites the existing file.
   	Physical table export settings	Select the scope of physical tables to export. Options: All tables or Tables created in Table Management. The default is All tables. All tables: Exports all tables under the corresponding engine in the source tenant. This does not include logical tables, materialized views, or temporary tables. Tables created in Table Management: Exports only tables created in Table Management. These tables have no history of external changes.

6. Click Export Release Package to start the export process.

   • Click Save Release Package. A draft record is created on the release package list page. You can edit this record.

   • Click Save and Preview to create a draft record and open the content preview page, where you can review the export configuration and package details. Click Back to Edit at the bottom of the page or click Edit next to Basic information or Export information to return to the package editing page.

   • The export process can take from minutes to hours, depending on the amount of data.