Visual artifact migration overview
Artifact migration allows you to export and import visual artifacts between Cloudera Data Visualization environments. Common use cases include promoting content from development or testing environments to production, creating backups, and sharing dashboards or applications with other users.
Cloudera Data Visualization supports both manual migration through the user interface and automated migration using REST APIs.
How artifact migration works
When you export a visual artifact, Cloudera Data Visualization generates a JSON file containing the artifact definition and its dependencies. The export includes information such as layouts, configurations, datasets, custom styles, and query definitions, but it does not include the underlying data or query results.
Dependencies are exported automatically. When the artifact is imported into another environment that has access to the required data sources, it appears and functions the same way as in the source environment.
During import, Cloudera Data Visualization checks whether an artifact with the same UUID already exists. If a match is found, the existing artifact is updated instead of creating a duplicate.
Supported visual artifacts
The migration utility supports the following artifact types:
- Datasets
- Linked visuals
- Dashboards
- Applications
- Custom styles
- Custom color palettes
- Segments
- Static assets
The export utility also includes existing thumbnails. During import, you can choose whether to:
- Import existing thumbnails
- Generate new thumbnails
- Skip thumbnail processing
Data compatibility requirements
The destination system must have access to the data used by the imported artifacts. The required tables must exist and be accessible through a valid data connection.
When the Check data table compatibility option is enabled, the import process verifies that all required tables are available. If a required table cannot be found, the import operation fails.
Some deployments use multiple data connections to access the same data. In these environments, you may need to disable the Check data table compatibility option during import. After the import completes, you can update datasets to use the appropriate data connections.
