The data types Stitch supports for replication fall into two categories:
-
Common, which are data types supported for all integrations.
Note: If a data type isn’t present in the Common data type list, it means that Stitch doesn’t currently support replication for that data type. Replicating columns with unsupported data types may lead to issues with replication.
-
Integration-specific, which are data types applicable only to specific integrations. For the sake of transparency, integration specific lists contain both supported and unsupported data types. Icons in the list indicate whether the data type is supported by Stitch.
As of June 19, 2018, the data types in the table below are supported for all integrations.
BIGINT | BIT | CHAR | DATE |
DECIMAL | DOUBLE | FLOAT | INTEGER |
LONGVARCHAR | LONGNVARCHAR | NCHAR | NVARCHAR |
NUMERIC | REAL | SMALLINT | TIME |
TIMESTAMP | TINYINT | VARCHAR |
The integrations listed below also have data types that are specific to them. Click the links for more info, including the level of support Stitch offers and the Stitch data type it will map to.
Columns with mixed data types
Occasionally Stitch will encounter a column that contains more than one data type. As Stitch requires that there be only one data type per column to properly type and store your data, columns containing multiple data types may be “split” to ensure all values are correctly typed.
For example: an order_confirmed
column is synced and typed as BOOLEAN
. In a subsequent sync, Stitch detects VARCHAR
values in this column.
As a result, Stitch will create an additional column to accommodate the VARCHAR
values. The new column name will be the original name appended with the data type: order_confirmed__string
How columns are named depends on the type of destination being used to warehouse data. Refer to the Mixed Data Types guide for more info.
Replicating unsupported data types
Columns containing data types that aren’t supported may prevent an entire table from replicating.
If you determine a non-replicating column contains an unsupported data type, you’ll need to de-select it to allow the table to successfully replicate.
‘Not Supported’ status for columns
If a column you want to sync has a Status of Not Supported
, the root cause may be an unsupported data type or insufficient user permissions.
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.