Notification of an upcoming change of behavior in Amazon Redshift V2 Connector
Product: Informatica Intelligent Cloud Services
Connector: Amazon Redshift V2
With the upcoming July 2021 release, when you migrate a Redshift V2 connection related mapping you can run the imported mapping using the target org’s connection, without any changes to the mapping attributes.
For example, you develop a mapping in the IICS development organization and you then migrate the mapping to the IICS production organization. When the connection endpoint or object path in the production organization differs, you can update the Redshift V2 connection to reflect the production endpoint. You do not have to modify the mapping again. Previously, you had to manually update the mapping and create the object in the production organization.
An Amazon Redshift V2 mapping that you migrate and run from the target environment fails when the Target transformation includes all of the following configurations:
The following image shows the configurations in the Target transformation that you need to consider:
If the target table specified in the Redshift V2 mapping at the object level has a primary key, but the table name specified as an override in the target advanced properties does not have a primary key defined, Data Integration considers the table name specified in the advanced properties. The mapping fails with the following error message:
[ERROR] <Target_table_name> No key is selected for Operation Type
When the mapping includes an update, upsert, or delete operation in the Target transformation, perform one of the following tasks before you move to the July 2021 release and migrate mappings from one environment to another: