MySQL
You can choose between two connector types for this destination:
- destination-mysql connector. Supports SSL and non-SSL connections.
- destination-mysql-strict-encrypt connector. Works like the connector above but supports SSL connections only.
Supported sync modes
| Sync mode | Supported? |
|---|---|
| Full Refresh - Overwrite | Yes |
| Full Refresh - Append | Yes |
| Full Refresh - Overwrite + Deduped | Yes |
| Incremental Sync - Append | Yes |
| Incremental Sync - Append + Deduped | Yes |
Get started with Airbyte Cloud
Airbyte Cloud only supports TLS-encrypted connections to your MySQL instance. Otherwise, follow the open-source instructions below.
Get started with Airbyte Open Source
Requirements
You’ll need the following to use the MySQL destination:
- To sync data to MySQL with typing and deduping: MySQL database 8.0.0 or above
- To sync data to MySQL without typing and deduping: MySQL 5.7 or above. The bundled MySQL Connector/J 9.x driver officially supports MySQL 8.0 and later. MySQL 5.7 is no longer supported upstream but still works with this connector.
- When SSL is enabled, the server must accept TLS 1.2 or TLS 1.3. SSL is enabled by default and is the only option on Airbyte Cloud. The driver no longer negotiates TLS 1.0 or TLS 1.1.
Troubleshooting
If the connection fails with Cannot create a PoolableConnectionFactory or an SSL handshake error, check that the server offers TLS 1.2 or later. This can affect older servers, such as an older Amazon RDS MySQL instance. Enable a supported TLS version on the server. You can’t configure the driver to fall back to TLS 1.0 or 1.1.
Network access
Make sure Airbyte can access your MySQL database. If your database is within a VPC, allow access from the IP you’re using to expose Airbyte.
Permissions
You need a MySQL user with CREATE, INSERT, SELECT, DROP permissions. An Airbyte-specific user is strongly recommended for this purpose.
Target database
MySQL doesn’t distinguish between a database and a schema. A database is essentially a schema containing all its tables. Choose an existing database or create a new one. This becomes the default database or schema for tables when the source doesn’t provide a namespace.
Set up the MySQL destination
Before setting up the MySQL destination in Airbyte, set the local_infile system variable to true. Run the SET GLOBAL local_infile = true query as a user with SYSTEM_VARIABLES_ADMIN permission. This is required because Airbyte uses LOAD DATA LOCAL INFILE to load data into the table.
You now have everything needed to configure MySQL as a destination in the UI. You’ll need the following information:
- Host
- Port
- Username
- Password
- Database
- jdbc_url_params (Optional)
Default JDBC URL parameters
Airbyte sets the following JDBC URL parameters. You can’t override them through the jdbc_url_params field:
useSSL=true(unlesssslis set to false)requireSSL=true(unlesssslis set to false)verifyServerCertificate=false(unlesssslis set to false)zeroDateTimeBehavior=convertToNullallowLoadLocalInfile=trueconnectionTimeZone=LOCAL(the connector writes and reads_airbyte_extracted_atin the connector’s own time zone; do not setconnectionTimeZoneor its aliasserverTimezoneinjdbc_url_params)
Known limitations
MySQL documentation explains identifier case sensitivity using the lower_case_table_names system variable. One recommendation is:
"It is best to adopt a consistent convention, such as always creating and referring to databases and tables using lowercase names.
This convention is recommended for maximum portability and ease of use."
As a result, the Airbyte MySQL destination forces all identifier names to lowercase. This includes table, schema and column names.
Connect through an SSH tunnel
Airbyte can connect to a MySQL instance through an SSH tunnel. This is useful when direct database access is impossible or against security policy. For example, the database might not have a public IP address.
An SSH tunnel connects Airbyte through an intermediate server, also called a bastion server. This server has direct access to the database. Airbyte connects to the bastion, which then connects directly to the database server.
This feature needs additional configuration when you create the destination. The following steps explain each setting.
-
Configure all destination fields as usual, except
SSH Tunnel Method. -
SSH Tunnel Methoddefaults toNo Tunnel, which means a direct connection. To use an SSH tunnel, chooseSSH Key AuthenticationorPassword Authentication.- Choose
Key Authenticationwhen using an RSA private key to establish the SSH tunnel. See below for more information about generating this key. - Choose
Password Authenticationwhen using a password to establish the SSH tunnel.
:::warning Airbyte Cloud requires encrypted communication. Select SSH Key Authentication or Password Authentication if you selected preferred as the SSL Mode. Otherwise, the connection will fail. :::
- Choose
-
SSH Tunnel Jump Server Hostidentifies the intermediate bastion server that Airbyte connects to. Enter a hostname or IP address. -
SSH Connection Portis the bastion server port used for the SSH connection. The default SSH port is22. Use the default unless you’ve explicitly changed the port. -
SSH Login Usernameis the username Airbyte uses to connect to the bastion server. This isn’t the MySQL username. -
If you’re using
Password Authentication, setSSH Login Usernameto the previous step’s user password. Leave this blank if you’re usingSSH Key Authentication. This isn’t the MySQL password. It’s the password for the OS user that Airbyte uses to run commands on the bastion. -
If you’re using
SSH Key Authentication, setSSH Private Keyto the RSA Private Key used for the SSH connection. Include the full key file contents, starting with-----BEGIN RSA PRIVATE KEY-----and ending with-----END RSA PRIVATE KEY-----.
Namespace support
This destination supports namespaces. MySQL doesn’t distinguish between a database and a schema. The configured database acts as the default namespace.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 1.1.2 | 2026-10-26 | 89768 | Upgrade MySQL Connector/J 8.0.22 to 9.6.0 and pin connectionTimeZone=LOCAL so typing no longer skips records on servers west of UTC (MySQL and MySQL Strict Encrypt destinations). |
| 1.1.1 | 2025-08-04 | 63736 | Use MySQL/MariaDB compatible timestamp format |
| 1.1.0 | 2025-03-25 | 50861 | add support for mariadb |
| 1.0.4 | 2025-03-24 | 56355 | Upgrade to airbyte/java-connector-base:2.0.1 to be M4 compatible. |
| 1.0.3 | 2024-12-18 | 49865 | Use a base image: airbyte/java-connector-base:1.0.0 |
| 1.0.3 | 2024-06-26 | 40566 | Remove strict-encrypt variant |
| 1.0.2 | 2024-06-26 | 40553 | Convert prod code to kotlin |
| 1.0.1 | 2024-06-25 | 40513 | Improve error reporting for “access denied” error |
| 1.0.0 | 2024-04-26 | 37322 | Remove normalization and upgrade to DV2 output format |
| 0.3.1 | 2024-04-12 | 36926 | Upgrade to Kotlin CDK |
| 0.3.0 | 2023-12-18 | 33468 | Upgrade to latest Java CDK |
| 0.2.0 | 2023-06-27 | 27781 | License Update: Elv2 |
| 0.1.21 | 2022-09-14 | 15668 | Wrap logs in AirbyteLogMessage |
| 0.1.20 | 2022-06-17 | 13864 | Updated stacktrace format for any trace message errors |
| 0.1.19 | 2022-05-17 | 12820 | Improved ‘check’ operation performance |
| 0.1.18 | 2022-02-25 | 10421 | Refactor JDBC parameters handling |
| 0.1.17 | 2022-02-16 | 10362 | Add jdbc_url_params support for optional JDBC parameters |
| 0.1.16 | 2022-02-14 | 10256 | Add -XX:+ExitOnOutOfMemoryError JVM option |
| 0.1.15 | 2021-12-01 | 8371 | Fixed incorrect handling “\n” in ssh key |
| 0.1.14 | 2021-11-08 | #7719 | Improve handling of wide rows by buffering records based on their byte size rather than their count |
| 0.1.13 | 2021-09-28 | #6506 | Added support for MySQL destination via TLS/SSL |
| 0.1.12 | 2021-09-24 | #6317 | Added option to connect to DB via SSH |
| 0.1.11 | 2021-07-30 | #5125 | Enable additionalPropertities in spec.json |
| 0.1.10 | 2021-07-28 | #5026 | Add sanitized json fields in raw tables to handle quotes in column names |
| 0.1.7 | 2021-07-09 | #4651 | Switch normalization flag on so users can use normalization. |
| 0.1.6 | 2021-07-03 | #4531 | Added normalization for MySQL. |
| 0.1.5 | 2021-07-03 | #3973 | Added AIRBYTE_ENTRYPOINT for kubernetes support. |
| 0.1.4 | 2021-07-03 | #3290 | Switched to get states from destination instead of source. |
| 0.1.3 | 2021-07-03 | #3387 | Fixed a bug for message length checking. |
| 0.1.2 | 2021-07-03 | #3327 | Fixed LSEP unicode characters. |
| 0.1.1 | 2021-07-03 | #3289 | Added support for outputting messages. |
| 0.1.0 | 2021-05-06 | #3242 | Added MySQL destination. |