Release Noteslink
June 2023link
We now support AWS PrivateLink for the following destinations:
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Aurora MySQL
- MariaDB MySQL
- MariaDB RDS MySQL
- MySQL
- MySQL RDS
- PostgreSQL
- SQL Server
- SQL Server RDS
July 2021link
We have implemented a new format (V2) for consistency in the destination configuration information. This format is valid for the following destinations:
For more information, see our V2 config format documentation.
January 2021link
We have fixed a bug where TIME values were sometimes synced to the destination incorrectly. Previously, we added a .0
to values with no decimals and dropped the hundredths place for values that did. We now sync TIME values to the destination as they appear in the source:
Source value | Destination value (with bug) | Destination value (fixed) |
---|---|---|
23:59:59 | 23:59:59.0 | 23:59:59 |
23:59:59.00 | 23:59:59.0 | 23:59:59.00 |
23:59:59.10 | 23:59:59.1 | 23:59:59.10 |
If any values were incorrectly synced prior to this change, you will need to initiate a historical re-sync or table re-sync to correct them.
June 2020link
We now replicate empty tables in a PostgreSQL source database as empty tables in the destination.
August 2019link
We have changed the MySQL version requirements for Fivetran to store data as JSON in a MySQL warehouse and create tables with primary keys.
We now convert JSON to text in versions below 5.7.8.
We now create primary keys in either of the following scenarios:
MySQL version earlier than 5.7.7:
- If the total number of primary keys provided by the source is less than 16, and the sum of the byte length of String primary keys is less than 191.
MySQL version 5.7.7 and later:
- If the total number of primary keys provided by the source is less than 16, and the sum of the byte length of String primary keys is less than 768.
January 2019link
Fivetran will create primary keys for a MySQL warehouse in either of the following scenarios:
MySQL version earlier than 5.7 or MariaDB version earlier than 10.2: If the source provides fewer than 16 primary keys and the sum of the byte length of string primary keys is less than 191.
MySQL version 5.7 and later or MariaDB version 10.2 and later: If the source provides fewer than 16 primary keys and the sum of the byte length of string primary keys is less than 768.
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
September 2018link
The MySQL warehouse now uses the load data infile strategy to write data. It requires the load_infile
system variable to be set to on
. For additional details, refer to our MySQL warehouse documentation.
August 2018link
String values will now be created as LONGTEXT
columns in the MySQL warehouse instead of VARCHAR
fields if they are not the primary key. We made this change to better handle MySQL's maximum row size limit.
April 2018link
If your destination uses a MySQL version earlier than 5.7, you can't use the timestamp
column as a primary key because MySQL incorrectly handles the decimal part of the timestamp. We now detect this scenario, skip tables with this column during our sync, and warn you to upgrade your destination MySQL version. Note that this limitation only applies to MySQL destinations, not MySQL sources.