Release Notes

August 2023

We now support Redshift Serverless as a destination.

March 2023

During UPDATE operations, we now insert null values for the VARBYTE columns that exceed 65535 bytes.

September 2022

We have added support for the VARBYTE data type. For connectors created on or after September 01, 2022, we convert BINARY data type to VARBYTE data type in your Redshift destination. For connectors created before September 01, 2022, we will continue to convert BINARY to VARCHAR type.

AWS PrivateLink is now generally available for Redshift.

For more information, see our Redshift setup guide.

September 2021

You can now use PrivateLink as a connection method for the following destinations:

• Redshift
• Snowflake

This feature is in BETA and available only for Business Critical accounts.

We have added automatic cluster region detection to the Redshift setup form. We now use your Host details to detect the cluster region automatically. For example, during the destination setup, if you enter the Host as datalake-test-cluster.czqj8z4xxnzl.us-west-1.redshift.amazonaws.com, we detect that the cluster region is us-west-1. If we can auto-detect the cluster region successfully, the Cluster region field will not be visible in the setup form.

August 2021

We have added support for the TIMESTAMP_TZ data type. For connectors created after August 30, 2021, we convert INSTANT data type to TIMESTAMP_TZ data type in your Redshift destination.

July 2021

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.

June 2021

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.

April 2021

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 2021-02-01T15:24:47.123456.

January 2021

You can now opt to use AWS IAM to authenticate Fivetran requests to your Redshift cluster. See our setup instructions for more information.

September 2020

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 destination. To learn how, see our Redshift setup guide.

June 2020

We now replicate empty tables in a PostgreSQL source database as empty tables in the destination.

July 2019

Fivetran no longer performs VACUUM DELETE for your Redshift destinations on the weekends, because Redshift now does it automatically. For more information on how Amazon Redshift schedules the VACUUM DELETE operation, see Amazon's changelog.

March 2019

We are changing our architecture to allow for much higher data throughput. Starting on April 30, 2019, all Fivetran connectors will originate from a new set of fixed IP addresses. For the US region, these IPs are:

• 35.227.135.0/29
• 35.234.176.144/29
• 52.0.2.4/32.

Update your IP safelists for the following databases and destinations before April 30. Not doing so will result in a connection failure.

Databases:

• MariaDB
• MongoDB
• MySQL
• Oracle
• PostgreSQL
• SQL Server

Destinations:

• Redshift
• Azure Synapse
• Snowflake

If you don't use any of the above databases or destinations with Fivetran, you don't need to take any action.

October 2018

For the following destinations, Fivetran now drops the primary_key field from existing tables in your destination if there is a primary_key coming in from your data source:

• MySQL
• PostgreSQL
• SQL Server
• Redshift

July 2018

We no longer sync system columns, such as oid, to your Redshift destination.

April 2018

We have changed the way we reclaim disk space from deleted rows. You can find additional details in our Redshift documentation.