Product and documentation updates about the MySQL integration from the team at Stitch.

Stay up-to-date by subscribing to our RSS feed.

MySQL integration: New version (v2) now in beta

A new version (v) of our integration is now in beta!

This version (v) of Stitch’s integration optimizes replication by utilizing Avro schemas to write and validate data, thereby reducing the amount of time spent on data extraction and preparation. Compared to previous versions of the integration, this version boasts increased performance and overall reduced replication time.

Notable improvements and changes in this version also include:

  • New column (field) naming rules. Avro has specific rules that dictate how columns can be named. As a result, column names will be canonicalized to adhere to Avro rules and persisted to your destination using the Avro-friendly name. Refer to the Column name transformations section in the docs for more info.
  • Expanded data type support. This version supports additional data types. Refer to the data types documentation for more info.

Note: The following features aren’t currently supported, but will be before the integration leaves beta:

  • Custom SSL certificates and certificate authorities

To get a look at how this version compares to the previous version of , refer to the version comparison documentation.

New feature: Integration changelogs

Introducing: Integration changelogs!

Check out the history of our integrations and stay in the loop on updates with dedicated changelogs for these integrations:

We’ll add changelogs for other popular integrations and destinations in the weeks to come. If there’s a specific integration you’d like to see us work on, let us know by creating an issue in the Stitch Docs GitHub repo.

MySQL (v1) integrations: Fix composite Primary Key sorting for Full Table Replication

Previously, the method used to bookmark Stitch’s place while replicating tables with composite Primary Keys resulted in some records being skipped. We’ve updated the query the integration uses to properly account for composite keys, ensuring replication will resume in the correct place.

MySQL (v15-10-2015) sunset

The v15-10-2015 version of our MySQL integration has been sunset. As of today, this version of the MySQL integration has been removed from Stitch and will no longer function.

Migrate to the latest version of MySQL (v1) today to continue replicating data.

MySQL (v1) integrations: Allow non-auto-incrementing Primary Keys for Full Table

Interruptible Full Table Replication now supports non-auto-incrementing Primary Keys!

Previously, this integration would only resume Full Table Replication if a table’s Primary Keys were auto-incrementing.

We’ve updated this feature to allow tables with non-auto-incrementing Primary Keys to be resumable if interrupted. Tables must have Primary Keys with one of the following data types to be interruptible if Full Table Replication is used:

  • DATE
  • CHAR
  • INT
  • TIME

MySQL (v1) integrations: Interruptible Full Table replication

Fullly replicating a table is now “interruptible,” meaning that, if the table uses auto-incrementing Primary Keys, replication for the table can span multiple replication jobs.

Previously, a table using Full Table had to be fully replicated in a single job. If the job was interrupted for any reason, Stitch would replicate the table from the beginning during the next job.

Now, if a replication job is interrupted for a (v) integration, tables using Full Table Replication that have auto-incrementing Primary Keys will resume replication from the last replicated record instead of re-replicating the entire table.

MySQL (v1) integrations: Binlog replication support

integrations can now use binlog replication to perform incremental replication in Stitch!

If you have binary logging enabled for your MySQL database, Stitch can now use it to help replicate your data. Log-based Incremental Replication allows for incremental replication of a table without a Replication Key and will capture and persist hard deletes.

This feature is now available as a Replication Method on the Table Settings of integrations. Check out the docs for more info.

MySQL (v15-10-2015) deprecation

The v15-10-2015 version of our MySQL integration has been deprecated. As of today, this version of the MySQL integration is no longer formally supported.

While connections using v15-10-2015 will continue to run, this version will be sunset in the future. Migrate to the latest version of MySQL (v1) today to prevent possible disruptions.

Extraction logs now available!

Detailed Extraction Logs are now available for select integrations in Stitch. This new feature presents detailed information about the extraction process in these integrations, and lets you:

  • Inspect, copy, and download extraction log files up to 50MB in size
  • View historical logs over the past seven days
  • Visualize how often extraction runs, how long it takes, and when it errors
  • View logs for extraction jobs currently in progress

This feature is available for the following integrations:

We’ll be working over the coming weeks to bring these logs to the rest of our integrations. Check out the docs for more info on this new feature.

MySQL (v1) integrations: Primary Keys can't be an unsupported data type

Previously, this integration would allow columns with unsupported data types to be included in the Primary Keys (key_properties) for a table. This has been corrected.

New version (v1) of MySQL integration

A new version (v) of our integration is now available!

Learn more about the integration and these features in our integration documentation.

Reset Replication Keys for database integrations

Need to completely re-replicate all incrementally replicated tables in a database integration? Now you can(!) via the Integration Settings page on any MySQL, PostgreSQL, Microsoft SQL Server, or MongoDB integration. Take care though - the re-replicated rows count towards your monthly caps.