The MySQL source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run.
The MySQL source does not alter the schema present in your database. Depending on the destination connected to this source, however, the schema may be altered. See the destination's documentation for more details.
MySQL data types are mapped to the following data types when synchronizing data:
If you do not see a type in this list, assume that it is coerced into a string. We are happy to take feedback on preferred mappings.
Note: arrays for all the above types as well as custom types are supported, although they may be de-nested depending on the destination. Byte arrays are currently unsupported.
Full Refresh Sync
Incremental - Append Sync
Replicate Incremental Deletes
SSH Tunnel Connection
Enabled by default
Create a dedicated read-only Airbyte user with access to all tables needed for replication
This is dependent on your networking setup. The easiest way to verify if Airbyte is able to connect to your MySQL instance is via the check connection tool in the UI.
This step is optional but highly recommended to allow for better permission control and auditing. Alternatively, you can use Airbyte with an existing user in your database.
To create a dedicated database user, run the following commands against your database:
CREATE USER 'airbyte'@'%' IDENTIFIED BY 'your_password_here';
The right set of permissions differ between the
CDC replication method. For
STANDARD replication method, only
SELECT permission is required.
GRANT SELECT ON <database name>.* TO 'airbyte'@'%';
CDC replication method,
SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT permissions are required.
GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'airbyte'@'%';
Your database user should now be ready for use with Airbyte.
STANDARD replication method this is not applicable. If you select the
CDC replication method then only this is required. Please read the section on CDC below for more information.
Your database user should now be ready for use with Airbyte.
If you need a record of deletions and can accept the limitations posted below, you should be able to use CDC for MySQL.
If your data set is small, and you just want snapshot of your table in the destination, consider using Full Refresh replication for your table instead of CDC.
If the limitations prevent you from using CDC and your goal is to maintain a snapshot of your table in the destination, consider using non-CDC incremental and occasionally reset the data and re-sync.
If your table has a primary key but doesn't have a reasonable cursor field for incremental syncing (i.e.
updated_at), CDC allows you to sync your table incrementally.
Make sure to read our CDC docs to see limitations that impact all databases using CDC replication.
Our CDC implementation uses at least once delivery for all change records.
You must enable binary logging for MySQL replication. The binary logs record transaction updates for replication tools to propagate changes.
You must enable binary logging for MySQL replication. The binary logs record transaction updates for replication tools to propagate changes. You can configure your MySQL server configuration file with the following properties, which are described in below:
server-id = 223344log_bin = mysql-binbinlog_format = ROWbinlog_row_image = FULLexpire_logs_days = 10
server-id : The value for the server-id must be unique for each server and replication client in the MySQL cluster. The
server-id should be a non-zero value. If the
server-id is already set to a non-zero value, you don't need to make any change. You can set the
server-id to any value between 1 and 4294967295. For more information refer mysql doc
log_bin : The value of log_bin is the base name of the sequence of binlog files. If the
log_bin is already set, you don't need to make any change. For more information refer mysql doc
binlog_format : The
binlog_format must be set to
ROW. For more information refer mysql doc
binlog_row_image : The
binlog_row_image must be set to
FULL. It determines how row images are written to the binary log. For more information refer mysql doc
expire_logs_days : This is the number of days for automatic binlog file removal. We recommend 10 days so that in case of a failure in sync or if the sync is paused, we still have some bandwidth to start from the last point in incremental sync. We also recommend setting frequent syncs for CDC.
Global transaction identifiers (GTIDs) uniquely identify transactions that occur on a server within a cluster. Though not required for a Airbyte MySQL connector, using GTIDs simplifies replication and enables you to more easily confirm if primary and replica servers are consistent. For more information refer mysql doc
Enable gtid_mode : Boolean that specifies whether GTID mode of the MySQL server is enabled or not. Enable it via
Enable enforce_gtid_consistency : Boolean that specifies whether the server enforces GTID consistency by allowing the execution of statements that can be logged in a transactionally safe manner. Required when using GTIDs. Enable it via
When a sync runs for the first time using CDC, Airbyte performs an initial consistent snapshot of your database. Airbyte doesn't acquire any table locks (for tables defined with MyISAM engine, the tables would still be locked) while creating the snapshot to allow writes by other database clients. But in order for the sync to work without any error/unexpected behaviour, it is assumed that no schema changes are happening while the snapshot is running.
Add AIRBYTE_ENTRYPOINT for Kubernetes support
Fix excessive logging for CDC method
Fix CDC handle tinyint(1) and boolean types
Fix max integer value failure
MySQL CDC poll wait 5 minutes when not received a single record
MySQL CDC poll 5s to 5 min
Implemented MySQL CDC
Fix bug in tests
Add NCHAR and NVCHAR support to DB and cursor type casting
Add an optional
Destination supports destination sync mode
Sources support primary keys
Protocol allows future/unknown properties
Migrate AbstractJdbcSource to use iterators
Fix NPE in State Decorator
Fix JdbcSource handling of tables with same names in different schemas
Fix JdbcSource OOM
Migrate Postgres and MySQL to use new JdbcSource
Support incremental sync
Add connectors using an index YAML file