All Products
Search
Document Center

Dataphin:Export A Full Release Package

Last Updated:Sep 16, 2026

A full export of a release package lets you quickly copy all objects from a source environment to a destination environment.

Prerequisites

  • You have configured publishing credentials, the storage location for the release package, permission checks, and approval settings in Cross-tenant publish settings. For more information, see Cross-tenant publish settings.

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

Limitations

During a cross-tenant deployment, you can only export the individual account of a quality rule's owner.

Permissions

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

Procedure

  1. Log on to Dataphin with an account authorized for cross-tenant deployment.

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

  3. In the left-side navigation pane, choose Cross-tenant publish > Export release package.

  4. On the Export release package page, click Create release package.

  5. On the Create release package page, configure the following parameters.

    Parameter

    Description

    Basic information

    Package name

    • The system generates a default name for the release package, which you can modify based on your business requirements. The format of the release file is tenant_name_generation_time.dp.

    • During a cross-tenant deployment, the destination environment only accepts release packages in the .dp format.

    • The package name cannot start with a period (.) or a space.

    • The package name cannot contain the following characters: question mark (?), 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.

    Package description

    Enter a description for the release package. The description can be up to 64 characters long.

    Export information

    Export object settings

    • Export Method: Select Full Export.

    • table creation statement: Choose to Export or Do not export table creation statements. If you choose to export them, the process queries metadata from the compute engine, which can be time-consuming depending on the engine's performance.

    Compute source export settings

    • Connection Information: The default option is Retain. You can also select Clear.

    • Authentication Information: The default option is Clear. You can also select Retain.

      Warning

      If you retain authentication information, the credentials for the compute source are included in the release package. To prevent security risks, handle the package file with care and do not share it.

    Data source export settings

    • Connection Information: The default option is Retain. You can also select Clear.

    • Authentication Information: The default option is Clear. You can also select Retain.

      Warning

      If you retain authentication information, the credentials for the data source are included in the release package. To prevent security risks, handle the package file with care and do not share it.

    Standard export settings

    This feature is available only if Data Standard is enabled. Use this setting to filter the mappings exported from the source environment.

    • Export only manually added mappings: Exports mappings that have been added manually. This includes mappings imported in batches from Excel files and mappings associated during the development process.

    • All mappings: Exports all mappings from the source environment.

    Security export settings

    This feature is available only if Data Security is enabled. Use this setting to filter the key values and security identification results exported from the source environment.

    • Key value: Choose whether to export the key value.

      • Export: The key value is exported from the source environment and can be used immediately after being imported into the destination environment.

      • Do not export: Exports the key name and type but not its value. You must regenerate or enter the key value after importing it into the destination environment.

        Note

        Key values are sensitive data. The system encrypts them during export and decrypts them after import.

    • Security identification result: Choose whether to export only manually specified results or all identification results.

      • Export only manually specified results: Exports results that were manually specified in the production environment. This includes results uploaded in batches from Excel files and results added manually.

      • All identification results: Exports all identification results from the production environment of the source tenant.

    Dump settings

    After you Enable OSS storage in the Cross-tenant publish settings, the dump settings appear on the Export File page. The exported release package is automatically stored in the specified OSS storage location.

    • Automatically dump to external storage upon completion: This option is deselected by default. If selected, the release package is automatically stored in the specified OSS storage location after the export is successful.

    • Duplicate file handling: Supports Rename, Ignore, and Overwrite.

      • Rename: Automatically renames the release file. If a file with the same name exists, Copy N is appended to the filename. If that name also exists, the number is incremented to N+1.

      • Ignore: Skips the current dump operation.

      • Overwrite: Replaces the existing file.

    Physical table export settings

    Select the export scope for physical tables. You can select All tables or Tables created in Table Management. The default is All tables.

    • All tables: Exports all tables from the corresponding engine in the source tenant. This does not include logical tables, materialized tables, or temporary tables.

    • Tables created in Table Management: Exports only the tables that were created in Table Management. These are tables that have no history of being modified externally.

  6. Click Export release package to start the export.

    • Click Save release package to save the configuration as a draft in the package list. You can edit this draft later.

    • Click Save and Preview to save the configuration as a draft and automatically go to the export preview page. On this page, you can review the export configuration and the objects to be exported. Click Back to Edit at the bottom of the page or the Edit button next to Basic information or Export information to return to the editing page.

    • The export time varies with the data volume and ranges from a few minutes to several hours.