Page tree

Trifacta Dataprep


Contents:

On April 28, 2021, Google is changing the required permissions for attaching IAM roles to service accounts. If you are using IAM roles for your Google service accounts, please see Changes to User Management.

   

Contents:


An exported flow can be imported into  Cloud Dataprep by TRIFACTA® INC..

Limitations

You cannot import flows that were exported before Release 6.8.


NOTE: You cannot import flows into a version of the product that is earlier than the one from which you exported it. For example, if you develop a flow on free Trifacta Wrangler, which is updated frequently, you may not be able to import it into other editions of the product, which are updated less frequently.

Imported flows do not contain the following objects:

NOTE: Depending on the import environment, some objects in the flow definition may be incompatible. For example, the connection type may not be valid, or a datasource may not be reachable. In these cases, the objects may be removed from the flow, or you may have to fix a reference in the object definition. After import, you should review the objects in the flow to verify.


  • Reference datasets
  • Samples

Imported datasets that are ingested into backend storage for  Cloud Dataprep by TRIFACTA INC. may be broken after the flow has been imported into another instance. These datasets must be reconnected to their source. You cannot use import mapping rules to reconnect these data sources. This issue applies to the following data sources:



Import into a new Google Cloud Platform project

When a flow is imported from one Google Cloud Platform (GCP) project into another GCP project, the underlying data must be accessible through the imported flow in the new GCP project. This means:

  • Source data must be accessible to all users who have access to the imported flow. Please see Cross-Project Data Access for more details.
  • If the flow is shared with other users of the project, they must have access to the underlying data.
  • Samples must be re-created, since they are not included in the import.

NOTE: If the above requirements are not met for flows imported into a different project, users may experience 403 Access Forbidden errors when attempting to connect to the flow or its underlying assets.

NOTE: If you import a flow from Cloud Dataprep Premium by TRIFACTA INC. into Cloud Dataprep Standard by TRIFACTA INC., you may encounter soft validation errors during job execution. If the imported flow uses custom VPC mode, then the job execution may fail, since network may be inaccessible. The workaround is 1) to set the VPC mode to Auto or 2) set accessible VPC options before you run your job. See Dataflow Execution Settings.

NOTE: If your imported flow contains an output object where dataflow execution overrides have been specified, then the overrides are applied to any jobs executed in the project where the flow was imported. Property values that do not appear in the imported output object are taken from the Project Settings page of the new project. See Dataflow Execution Settings.


Import


NOTE: When you import a flow, you must import a ZIP file containing the JSON definition.

Steps:

  1. Export the flow from the source system. See Export Flow.
  2. Login to the import system, if needed.
  3. Click Flows.
  4. From the context menu in the Flow page, select Import Flow.
  5. Select the ZIP file containing the exported flow. Click Open.

The flow is imported and available for use in the Flows page.

This page has no comments.