We have added a new destination setup test. Now, we validate the cluster region you specify in the setup form. We skip the test if you don’t select the cluster region.
We have added support for the SUPER data type to store JSON data. For source connectors created after July 28, 2021, we convert JSON data type to SUPER data type in your Redshift destination. For instructions on how to query your JSON data, see Query JSON data.
We have added a new optional field, Cluster region, to the destination setup form. You can now choose the AWS Region of your S3 bucket. Fivetran will use the data staging bucket in the cluster region you select. If you use VPC security policies, you must select the same region as the Redshift cluster. If you do not specify the cluster region, we will use your data processing location as the cluster region.
We have added a new optional field, Cluster ID, to the destination setup form. If you authenticate using IAM and use an SSH tunnel to connect, you must enter the Cluster ID and the Cluster region.
We have added a new setup test to validate if you have provided the Cluster ID and Cluster region details in the setup form. We perform this test only if you use IAM authentication and an SSH tunnel to connect.
We now truncate LOCALDATETIME values to microsecond precision before we load them as TIMESTAMP values to your Redshift destination. For example, if we receive a LOCALDATETIME value
2021-02-01T15:24:47.1234567, we truncate the value and write it to your destination as
We have added a new test in the Redshift destination setup form to verify CREATE TEMPORARY TABLES permissions. When you set up your Redshift destination, you must grant the
fivetran user permission to create temporary tables in your Redshift warehouse. To learn how, see our Redshift setup guide.
- Fivetran no longer performs
VACUUM DELETEfor your Redshift warehouses on the weekends, because Redshift now does it automatically. For more information on how Amazon Redshift schedules the
VACUUM DELETEoperation, check out Amazon’s changelog.
For the following warehouses, Fivetran now drops the
primary_key field from existing tables in your warehouse if there is a
primary_key coming in from your data source:
- SQL Server
We no longer sync system columns, such as
oid, to your Redshift warehouse.
We have changed the way we reclaim disk space from deleted rows. You can find additional details in our Redshift documentation.