September 2021link
You can now use PrivateLink as a connection method for the following destinations:
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 2021link
We have added support for the TIMESTAMP_TZ data type. For source connectors created after August 30, 2021, we convert INSTANT data type to TIMESTAMP_TZ data type in your Redshift destination.
July 2021link
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 2021link
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 2021link
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 2021link
You can now opt to use AWS IAM to authenticate Fivetran requests to your Redshift cluster. See our setup instructions for more information.
September 2020link
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.
July 2019link
- 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 theVACUUM DELETEoperation, check out Amazon’s changelog.
October 2018link
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:
- MySQL
- PostgreSQL
- SQL Server
- Redshift
- Periscope
- Panoply
July 2018link
We no longer sync system columns, such as oid, to your Redshift warehouse.
April 2018link
We have changed the way we reclaim disk space from deleted rows. You can find additional details in our Redshift documentation.