Snowflake columns mapping
Type mapping
The system matches Snowflake data types to Data Integration data types while extracting your data. If a data type is not supported, the platform maps as a String type.
The following table shows the mapping of Snowflake data types to Data Integration-compatible types:
| Data Integration Type | Snowflake Type |
|---|---|
| STRING | STRING |
| INTEGER | NUMBER |
| FLOAT | FLOAT |
| BOOLEAN | BOOLEAN |
| TIMESTAMP | TIMESTAMP |
| TIMESTAMP | DATE |
| RECORD | VARIANT |
| VARIANT | VARIANT |
| OBJECT | VARIANT |
Scenarios of data type conflicts
If you update the datatype of an existing source column and a mismatch occurs, the platform applies defined rules to determine the datatype of the corresponding target column, resolving the conflict. These rules select the most comprehensive data type to maintain data integrity and prevent information loss.
Examples of data type conflicts
The table below outlines scenarios of data type conflicts and the resolution rules. The Inferred Type column represents the chosen data type in the target table when there is a conflict.
| Conflicting Types | Inferred Type | Example Scenario |
|---|---|---|
| TIMESTAMP vs. DATE | TIMESTAMP | If a column in the source initially uses the TIMESTAMP type, but changes to DATE, the target converts it to TIMESTAMP. |
| SMALLINT vs. BOOLEAN | SMALLINT | A conflict between SMALLINT and BOOLEAN types in the source column leads to the target column adopting the SMALLINT type. |
| INTEGER vs. (SMALLINT / BOOLEAN) | INTEGER | If an INTEGER is SMALLINT or BOOLEAN in the source, promoted to INTEGER in the target. |
| BIGINT vs. (INTEGER / SMALLINT / BOOLEAN) | BIGINT | If a column of BIGINT type, but changes to SMALLINT, BOOLEAN, or INTEGER in the source, it elevates to BIGINT in the target. |
| DECIMAL vs. (INTEGER / BIGINT / SMALLINT / BOOLEAN) | DECIMAL | If a source column is INTEGER or DECIMAL, the target transforms it into DECIMAL.. |
| DOUBLE PRECISION vs. (INTEGER / BIGINT / SMALLINT / BOOLEAN) | DOUBLE PRECISION | If there is a conflict between DOUBLE PRECISION and SMALLINT in the source column, the target column adopt DOUBLE PRECISION. |
| REAL vs. (DOUBLE PRECISION / DECIMAL / INTEGER / BIGINT / SMALLINT / BOOLEAN) | REAL | If there is a change in the a column of DOUBLE PRECISION type to REAL type in the source, it remain as REAL in the target. |
| FLOAT vs. (INTEGER / BIGINT / SMALLINT / DECIMAL / REAL / DOUBLE PRECISION / BOOLEAN) | FLOAT | A source column initially of FLOAT type changed to INTEGER remain as FLOAT in the target. |
| STRING vs. ALL DATATYPES | STRING | If a source column is initially set as STRING type and later changed to TIME or INTEGER, treated as STRING type in the target. |
| VARIANT vs. ALL DATATYPES | VARIANT | If a column in the source is VARIANT type and updated to INTEGER type, the target column retains the VARIANT type. |
VARCHAR and OBJECT have higher priority and overrides other data types in conflicts.
