Before you import a packaged flow into a new environment, you may need to apply import rules to remap objects and locations from the source instance to the new instance. Import mapping rules are not required when importing into the same environment, although they may be helpful in some cases.

• For more information on creating an export package, see Export Flow.
• For more information on how to import, see Import Flow.

You can apply the following types of remappings:

Import Rules

When a flow is imported, references in the flow definition that apply in the source instance may not apply in the target instance. For example, the location paths to the source datasets may need to be rewritten to point to a different location in the target instance. 

Before you import your flow definition, you need to define rules for any value or object remapping that must be done in the target environment. 

Notes on import rules

1. Value and object remapping rules should be completed before you import the flow definition. The flow may be non-functional until the rules are applied.
   

   Tip: After you create your import rules, you can perform via API a dry run of the import. Any errors are reported in the response. Details are provided below.

   
   

2. Value and object remapping rules are applied at the time of import. If you add new rules, they are not retroactively applied to release packages that have already been imported.
3. When changing rules:
   1. Any previously rules applied to the same import object are deleted.
   2. You can apply multiple rules in the same change. 
   3. Rules are applied in the order in which they are listed in the request. Rules listed later in the request must be compatible with expected changes applied by the earlier rules. 
4. In this release, value and object remapping must be completed via API. API usage is considered a developer-level skill. Examples are provided below.

Import Rule Requirements

Examples

The following are some example import rules to address specific uses.

Example - Replace a connection

In this following example, you must remap the connection from the source instance of the platform to the corresponding connection in the instance where you are importing. 

First, you must be able to uniquely identify the connection from the source that you wish to remap. 

• While the connection Id may work in a limited scope, that identifier is unlikely to be unique within your environment.
• If you do know the connect Id from the source system, you can skip the first step below.

In the API response in a connection definition, you can acquire the uuid value for the connection, which is a unique identifier for the connection object across all instances of the platform:

/v3/connections

GET

{
    "data": [
        {
            "connectParams": {
                "vendor": "postgres",
                "host": "localhost",
                "port": "5432",
                "database": "trifacta"
            },
            "id": 10,
            "host": "localhost",
            "port": 5432,
            "vendor": "postgres",
            "params": {
                "connectStrOpts": "",
                "database": "trifacta"
            },
            "ssl": false,
            "name": "postgres",
            "description": "",
            "type": "jdbc",
            "createdBy": 1,
            "isGlobal": false,
            "credentialType": "basic",
            "credentialsShared": true,
            "uuid": "7d173c90-c4e1-11e7-a768-71cd1fa636c3",
            "createdAt": "2017-11-09T00:04:00.345Z",
            "updatedAt": "2017-11-09T00:04:00.345Z",
            "updatedBy": 1,
            "credentials": [
                {
                    "username": "<myUserId>"
                }
            ]
        },
        {
            "connectParams": {
                "vendor": "hive",
                "host": "hadoop",
                "port": "10000",
                "jdbc": "hive2",
                "defaultDatabase": "default"
            },
            "id": 1,
            "host": "hadoop",
            "port": 10000,
            "vendor": "hive",
            "params": {
                "jdbc": "hive2",
                "connectStringOptions": "",
                "defaultDatabase": "default"
            },
            "ssl": false,
            "name": "hive",
            "description": null,
            "type": "jdbc",
            "createdBy": 1,
            "isGlobal": true,
            "credentialType": "conf",
            "credentialsShared": true,
            "uuid": "ae41c5a0-c460-11e7-8163-c3c02bb1fb0b",
            "createdAt": "2017-11-08T08:41:57.755Z",
            "updatedAt": "2017-11-08T08:41:57.755Z",
            "updatedBy": 1,
            "credentials": []
        }
    ],
    "count": {
        "owned": 2,
        "shared": 0,
        "count": 2
    }
}

In the above, you identify that the connection used for the exported flow is the Postgres one. This object has the following unique identifier:

"uuid": "ae41c5a0-c460-11e7-8163-c3c02bb1fb0b"

In the target system, you must now create a rule in the deployment into which you are importing that searches for this unique value. In the following example:

• The deploymentId is known to be 4.
• The connectionId to map the source connection is 1.

The uuid field in the import package is searched for the matching string. If it is found, the connection in the import package is replaced with the connection in the target system with an Id of 1:

/v3/deployments/4/objectImportRules

[{"tableName":"connections","onCondition":{"uuid": "ae41c5a0-c460-11e7-8163-c3c02bb1fb0b"},"withCondition":{"id":1}}]

{
    "deleted": []
}

To test your rule, perform a dry run of the import. See below.

Example - Remap an HDFS location

In this example, your import rule must remap the path to the source from your Dev paths to your Prod paths. Suppose the pattern looks like this:

Note the differences:

• The /dev/ part of the path has been replaced by /prod/.
• The filename is different.

You can use the following value import rules to change the path values. In the following example, the rules are applied separately.

/v3/deployments/4/valueImportRules

[
  {"type":"fileLocation","on":"/\/dev\//","with":"/prod/"}
  {"type":"fileLocation","on":"/\/([a-zA-Z0-9_]*).csv/","with":"$1-Prod.csv"},
]

{
    "deleted": []
}

To test your rule, perform a dry run of the import. See below.

Example - Remap an S3 location

For S3 sources, you can apply remapping rules including changing to a new S3 bucket. 

In this example, your import rule must remap the path to the source from your Dev paths to your Prod paths. Suppose the pattern looks like this:

You can use the following value import rules to change the bucket name and path values.

s3Bucket name rule: This rule replaces the name of the S3 bucket to use with the new one: wrangle-prod.

fileLocation rule: This rule uses regular expressions to match each segment of the path in the source bucket's paths. 

• Files are located at a consistent depth in the source bucket.
• Path segments and filename use only alphanumeric values and underscores (_). 
• The replacement path is shortened to contain only the parent name ($2) and the filename ($4) in the path.

/v3/deployments/4/valueImportRules

[
  {"type":"s3Bucket","on":"wrangle-dev","with":"wrangle-prod"},
  {"type":"fileLocation","on":"/\/([a-zA-Z0-9_]*)\/([a-zA-Z0-9_]*)\/([a-zA-Z0-9_]*)\/([a-zA-Z0-9_]*).csv/","with":"/$2/$4.csv"},
]

{
    "deleted": []
}

To test your rule, perform a dry run of the import. See below.

Import Dry-Run

After you have specified a set of import rules, you can perform a dry-run of an import of an import package. This dry-run does not perform the actual import but does report any permissions errors or other issues in the response. 

In this example, the flow2import.zip file contains the package to import into deployment 4. 

/v3/deployments/4/releases/dryRun

{    "importRuleChanges": {
        "object": [],
        "value": []
    },
    "flowName": "POS-r01 Flow"
}

 After the above dry-run has been executed, the import package can be imported and is automatically connected to the appropriate connection. See API Releases Create v3.