Fivetran Status Pagelink
You can now check the status of the Fivetran Web APP, API, and Replication Servers by visiting [https://status.fivetran.com/](https://status.fivetran.com/).
You can also subscribe to our status page to receive updates on any incidents via email.
MySQL Invalid Time Valueslink
Fivetran no longer supports invalid
Timestamp values. For example,
2019-00-01 00:00:00 is invalid. This change immediately affects all new MySQL connectors, and we will roll it out gradually to existing connectors.
The supported ranges of
Timestamp in MySQL are:
|Date||'1000-01-01' to '9999-12-31'|
|Datetime||'1000-01-01 00:00:00' to '9999-12-31 23:59:59'|
|Timestamp||'1970-01-01 00:00:01' UTC to '2038-01-19 03:14:07' UTC|
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
Sync records from the Heap platform. Heap is an automation tool for user analytics.
We have added four new tables:
- `PROJECT` table with the fields: - `id` - `repository_id` - `creator_id` - `body` - `number` - `state` - `name` - `created_at` - `updated_at` - `is_deleted`
COLUMNtable with the fields:
CARDtable with the fields:
ISSUE_PROJECT_HISTORYtable with the fields:
is_deletedcolumn to the
MILESTONEtable to capture deletes.
Version 1.0 of the Help Scout API is now deprecated. Version 2.0 of the Help Scout API has caused major changes in the schema. The new schema contains the following tables:
HAPPINESS_RATING, all tables have become history tables and have the word
HISTORY appended to indicate that.
Each history table has an
updated_at field which is a part of the primary key. When a record is updated, its
updated_at changes, and so does its primary key. Thus, the older record remains preserved as history.
We have temporarily removed two tables. Help Scout didn't include an endpoint for these two tables in version 2.0 of their API. Once they add the endpoint, we will sync these two tables again:
Optimizely has introduced a new way to access your processed results data via an S3 export. We have added two tables to support access to that data:
RESULT table with the fields:
RESULT_SEGMENT table with the fields:
We now provide
segmentio metadata in
purchase_idcolumn to the
PURCHASE_ORDER_LINKED_TXNtable to support
linked_bill_payment_idcolumn to the
BILL_PAYMENT_LINEtable to support
gramscolumns to the
We now require you to configure a Role ARN when you set up an Amazon S3 connector, even if your bucket is a public bucket.
Existing Amazon S3 connectors will not be affected. However, if you reconfigure an existing connector or create a new one, you will have to configure a Role ARN even if your bucket is a public bucket.
We have added a new connection test to the Amazon S3 setup form that helps you adopt security best practices. The test checks your bucket policy settings to make sure you have created your Role ARN using the given externalID.
If you mistakenly create your Role ARN without using the give externID, the configuration will now fail the test. You will have to correct your Role ARN.
We have released a new version of the AppsFlyer connector.
We have split the
EVENTtable from the old version into two new tables:
DATA_LOCKER_EVENTStable captures events from AppsFlyer Data Locker. The
WEBHOOK_EVENTStable captures webhook events.
We have removed the following tables:
The new version supports AppsFlyer Data Locker 2.0
The new version resolves a data integrity issue with events and webhooks. Fivetran now better captures events from AppsFlyer Data Locker and webhooks.
We now use the GitHub Webhook API. It allows us to make incremental updates faster and capture deletes for the following tables:
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.
We can now sync changes to primary keys.
- For each table where the primary key is expected to change, you need to run the following query:
ALTER TABLE "<schema>"."<table>" ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS
- If you don't configure the logging data correctly, you will receive a warning when Fivetran encounters a primary key change. The warning will give you customized instructions.
- This improvement will roll out to customers over the next month.
We now exclude the
ORGANIZATION_MEMBERSHIP table from the sync by default because it can be a large table and may degrade performance.
If you wish to sync
ORGANIZATION_MEMBERSHIP go to the schema tab of your Fivetran dashboard and select it.