Migrating a connector from previous versions using the Data Integration REST API

Back Next

Migration guidelines and restrictions

This section includes the connections that you can migrate and the properties in the referenced assets of the connection that are applicable for migration. This section also describes guidelines and restrictions that are applicable for the connection migration.

When you migrate, the configured advanced properties and the field mappings in mappings and tasks from the old connection version are retained in the current version. However, due to differences between the old and current connection versions, some transformations, fields, functions, expressions, or data types might not be valid or might be valid with restrictions for the migration.

Consider the following general guidelines when you migrate a connection to the current version:

If a connection is used in synchronization tasks or mappings configured in advanced mode, these assets are not updated with the new connection.

You can migrate a connection referenced in multiple assets in one migration call. However, you cannot migrate connections when multiple transformations in the asset use different connection names or different connection types. If the connection names or types used in an asset are not the same, you need to migrate each transformation in the asset in different migration calls.

For example, you have an Amazon S3 V1 mapping that consists of a connection named S3V1 in the Source transformation and a separate connection named S3_V1 in the Target transformation. When you post a request using the migration API for the connection name, S3V1, the mapping is updated, where the Source transformation now references the current connection. To update the same asset that uses the S3_V1 connection in the Target transformation, you need to post another request to migrate the S3_V1 connection.

If the old connection is referenced in a completely parameterized mapping, migration applies only if the asset uses the following parameterization combinations:

The mapping uses a connection and object, where both are parameterized.

The mapping uses a connection that is not parameterized, while the object is parameterized.

If the mapping contains a parameterized connection, but if the object is not parameterized, the old connection in the asset is not switched with the new connection.

Migrating a connector from previous versions using the Data Integration REST API

Amazon Redshift

Amazon S3

Microsoft Azure Blob Storage

Microsoft Azure Synapse SQL

Snowflake

Download Guide

Watch

Comments

Cloud Data Integration Homepage

Free Trial

Communities