Snowflake Cloud Data Warehouse V2 Connector > Additional runtime configurations > Dynamic schema handling for mappings and elastic mappings
  

Dynamic schema handling for mappings and elastic mappings

You can choose how Data Integration handles changes that you make to the data object schemas. To refresh the schema every time the task runs, you can enable dynamic schema handling in the task.
A schema change includes one or more of the following changes to the data object:
Configure schema change handling on the Schedule page when you configure the task.
The following table describes the schema change handling options:
Option
Description
Asynchronous
Default. Data Integration refreshes the schema when you edit the mapping, elastic mapping, or task, and when Informatica Intelligent Cloud Services is upgraded.
Dynamic
Data Integration refreshes the schema every time the task runs.
You can choose from the following options to refresh the schema:
  • - Alter and apply changes. Data Integration applies the following changes from the source schema to the target schema:
    • - New fields: Alters the target schema and adds the new fields from the source.
    • - Renamed fields: Adds renamed fields as new columns in the target.
    • Note: To include schema changes for renamed or new fields, see Schema handling for renamed or added columns in elastic mappings.
    • - Data type and precision updates. Applies these changes to the target.
    • Note: Updates to the scale are not applicable.
    • - Deleted fields: Ignores deleted fields.
  • - Don't apply DDL changes. Data Integration does not apply the schema changes to the target.
  • - Drop current and recreate. Drops the existing target table and then recreates the target table at runtime using all the incoming metadata fields from the source.
For more information, see the "Schema change handling" topic in Tasks in the Data Integration help.

Schema handling for renamed or added columns in elastic mappings

When you run an elastic mapping, if a column is renamed or a field is added to the source, the target schema is jumbled because of the difference in columns in the source and target schema.
To avoid this, you must set the following properties, separated by an ampersand, in the Additional Write Runtime Parameters field in the Target transformation:
When you set these properties, Data Integration includes the name and also ignores any mismatch between the source and target schema when the column names contain uppercase letters, digits, or underscore.
If the column names do not contain uppercase letters, you must additionally set the keep_column_case=on parameter in both the Source and Target transformations:

Rules and guidelines for dynamic schema handling in elastic mappings

Consider the following rules and guidelines when you enable dynamic schema change handling for elastic mappings:

Rules and guidelines for dynamic schema handling in mappings

Consider the following rules and guidelines when you enable dynamic schema change handling for mappings: