Release Notes

July 2024

All new MySQL connectors now support Fivetran Teleport Sync for tables without primary keys. Learn more in our MySQL Fivetran Teleport Sync documentation.

May 2024

Our GTID replication mode is now generally available.

March 2024

Our MariaDB and MySQL connectors now support the TRUNCATE command.

January 2024

We now support replication using global transaction identifiers (GTIDs). In GTID mode, we stream incremental updates from your database using each transaction's GTID instead of its binary log position.

June 2022

Fivetran Teleport Sync is now generally available. Learn more in our Fivetran Teleport Sync for MySQL documentation.

March 2022

Fivetran Teleport Sync is now available in beta. Learn more in our Fivetran Teleport Sync for MySQL documentation.

May 2021

To correct data integrity issues, we will now trigger a re-sync for a table when we detect a reduction in the size of one of its SET columns. Before the re-sync begins, you may notice a SET type change detected error in your logs.

When we detect a reduction in the size of a table's ENUM columns, we now create an ENUM type change detected error in your logs before we trigger a re-sync for that table. Previously, we added FIVETRAN_ERROR_ENUM_DELETED values to your ENUM columns before we triggered a re-sync.

March 2021

Data syncs no longer fail without explanation when we encounter prohibited DATETIME values (for example, 29 Feb 2021). How we respond to prohibited values varies by sync type:

• Initial syncs: The sync fails when it encounters a prohibited value. We create a Task in your Fivetran dashboard with instructions on how to resolve the issue.

• Incremental updates: The sync does not fail when it encounters a prohibited value. We process the prohibited value and create a Warning in your Fivetran dashboard with instructions on how to resolve the issue. The way we process the prohibited value depends on your sync mode:

  • Soft delete mode: We ignore the prohibited value.
  • History mode: If the prohibited value is a primary key, we ignore it. If the prohibited value is not a primary key, we change it to NULL.

Learn more about Tasks and Warnings in our Alerts documentation.

February 2021

Our Azure Database for MySQL connector is now generally available.

See our Azure Database for MySQL setup instructions.

April 2020

We have increased the fractional second precision of our binary log parser from millisecond to microsecond for DATETIME, TIMESTAMP, and TIME types. To correct existing values of these types in your destination, trigger a table re-sync or a historical re-sync in the connector dashboard.

We now add a _fivetran_synced column while syncing empty tables and columns from the source.

We have added Magento MySQL and Magento MySQL RDS to the list of connectors that can be created via our REST API.

March 2020

We have fixed a problem where unsigned BIGINT values larger than 9223372036854775807 were sometimes parsed incorrectly during incremental updates. If any values were incorrectly synced prior to this change, you will need to initiate a re-sync to correct them.

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

To correct data integrity issues, we will now trigger a re-sync for a table when we detect a reduction in the size of one of its ENUM columns. Before the re-sync begins, you may notice FIVETRAN_ERROR_ENUM_DELETED values in these columns.

February 2020

We have added a new test, Check Binlog Retention Period, to the Amazon RDS for MySQL connector setup form. The test checks your binlog retention period and displays a warning if:

• Your MySQL database's binlog retention period is less than 24 hours
• You do not have permissions to access the mysql.rds_configuration table

October 2019

We are now rolling out support for BLOB, TINYBLOB, MEDIUMBLOB, LONGBLOB, and YEAR data types in version 4 of our MySQL connector.

We are now rolling out the ability to sync MySQL DATETIME columns to the destination as TIMESTAMP_NTZ columns for version 4 of our MySQL connector.

We have a fixed a bug that caused zeroed DATE and DATETIME values to sync incorrectly. MySQL allows 0000-00-00 and 0000-00-00 00:00:00 as values for DATE and DATETIME primary key columns respectively. Previously, we converted these values to 1970-01-01 and 1970-01-01 00:00:00. Therefore, zeroed times and the real values of 1970-01-01 and 1970-01-01 00:00:00 were mapped to the same value in the destination. Fivetran now converts these values as follows:

• DATE: from 1970-01-01 to -999999999-01-01
• DATETIME: from 1970-01-01 00:00:00 to -999999999-01-01 00:00:00

September 2019

If you have a logging service connected to your Fivetran account, the import progress of your tables in the event logs will be visible in your logs as an import_progress event. Table names will be in either the COMPLETE or IN_PROGRESS state, depending on their sync status. Tables that are not reported in the event have not started their import.

We have begun rolling out support for the following spatial types in version 4 of our MySQL connector:

• GEOMETRY
• GEOMETRYCOLLECTION
• LINESTRING
• MULTILINESTRING
• POINT
• MULTIPOINT
• POLYGON
• MULTIPOLYGON

August 2019

Fivetran has released version 4 of our MySQL connector, which offers improved sync reliability. We will add a number of upgrades to this version in the coming months:

• We will sync DATETIME values as TIMEZONE_NTZ values in your destination.

• We will support parsing for TRUNCATE DDL events.

• We will support the following new data types:

  • BINARY
  • VARBINARY
  • YEAR
  • BLOB
  • SMALLBLOB
  • MEDIUMBLOB
  • LONGBLOB
  • GEOMETRY
  • GEOMETRYCOLLECTION
  • LINESTRING
  • MULTILINESTRING
  • POINT
  • MULTIPOINT
  • POLYGON
  • MULTIPOLYGON

We have begun rolling out support for BINARY and VARBINARY types.

For more information about data types, see our MySQL documentation.

June 2019

We have added a test to the MySQL setup forms which checks if you are using RDS. We added the test because if you select the wrong variant in the setup form, your connector may not work properly.

The test fails when there is a discrepancy between your selection and what Fivetran detected. If you are not confident in your selection, you may go back to the Add Connector view and select the connector type that matches your MySQL database variant.

Fivetran no longer supports invalid DATE, DATETIME, and TIMESTAMP values. For example, 2019-00-01 00:00:00 is invalid. This change immediately affects all new MySQL and MariaDB connectors, and we will roll it out gradually to existing connectors.

The supported ranges of DATE, DATETIME, and TIMESTAMP in MySQL are:

We will load these invalid values as NULL into the destination and display a warning on your Fivetran dashboard. The warning will indicate the schemas, tables, and columns which contain NULL values.

March 2019

Fivetran has added core support for the TIMESTAMP WITHOUT TIMEZONE data type. Up until now, Fivetran assumed that timestamps without timezone were in UTC. This addition means that for the following databases with a TIMESTAMP WITHOUT TIMEZONE type will replicate to a more correct destination type:

• MySQL
• Oracle
• PostgreSQL
• SQL Server

TIMESTAMP WITHOUT TIMEZONE support is immediately available for Oracle, PostgreSQL, and SQL Server. MySQL and MariaDB support will be released soon.

This change is backwards compatible. Fivetran will continue assuming UTC time zone if the destination type is TIMESTAMP WITH TIMEZONE. In order to get the more specific type, drop the table in the destination and re-sync the table in your Fivetran dashboard.

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.

February 2019

Azure Database for MySQL is a MySQL database service built on Microsoft's scalable cloud infrastructure for application developers.

See our Azure Database for MySQL setup instructions.

November 2018

You can now trigger re-syncs of individual tables from your Fivetran dashboard:

The re-sync button appears when you hover your cursor over the row that contains the table name.

This feature is available for the following connectors:

• Amazon DynamoDB
• MongoDB
• MySQL
• NetSuite SuiteAnalytics
• Oracle
• PostgreSQL
• Salesforce
• SQL Server
• Zuora

We have identified and fixed an extremely rare bug that can cause data to be missed during binary log replication. The bug meant that, in some cases, our system believed that all data had been successfully synced, when the binary log replication process had actually stopped prematurely.

September 2018

The MySQL connector is now able to handle unescaped control characters in textual data as if they had been properly escaped.

July 2018

You can now customize the replica ID used to access your database's binary logs. By default, the replica ID is a random integer greater than 1000.

May 2018

We now fully support the SET data type and consistently sync it as a JSON array. Previously, we synced SET as STRING during the initial import and as INT when processed from the binary logs. If any values were incorrectly synced prior to this change, you will need to initiate a re-sync to correct them.

MySQL on Google Cloud SQL is a fully-managed database service that makes it easy to set up, maintain, manage, and administer your MySQL relational databases on Google Cloud Platform.

See our Google Cloud SQL for MySQL setup instructions.