airbyte/docs/integrations/destinations/mysql.md

MySQL

Overview

The Airbyte MySQL destination allows you to sync data to MySQL.

Sync overview

Output schema

Each stream will be output into its own table in MySQL. Each table will contain 3 columns:

• _airbyte_ab_id: a uuid assigned by Airbyte to each event that is processed. The column type in MySQL is VARCHAR(256).
• _airbyte_emitted_at: a timestamp representing when the event was pulled from the data source. The column type in MySQL is TIMESTAMP(6).
• _airbyte_data: a json blob representing with the event data. The column type in MySQL is JSON.

Features

Feature	Supported?(Yes/No)	Notes
Full Refresh Sync	Yes
Incremental - Append Sync	Yes
Namespaces	Yes

Getting started

Requirements

To use the MySQL destination, you'll need:

• A MySQL database version 5.7.8 or above

Setup guide

Network Access

Make sure your MySQL database can be accessed by Airbyte. If your database is within a VPC, you may need to allow access from the IP you're using to expose Airbyte.

Permissions

You need a MySQL user with CREATE, INSERT, SELECT, DROP permissions. We highly recommend creating an Airbyte-specific user for this purpose.

Target Database

MySQL doesn't differentiate between a database and schema. A database is essentially a schema where all the tables live in. You will need to choose an existing database or create a new database. This will act as a default database/schema where the tables will be created if the source doesn't provide a namespace.

Setup the MySQL destination in Airbyte

Before setting up MySQL destination in Airbyte, you need to set the local_infile system variable to true. You can do this by running the query SET GLOBAL local_infile = true with a user with SYSTEM_VARIABLES_ADMIN permission. This is required cause Airbyte uses LOAD DATA LOCAL INFILE to load data into table.

You should now have all the requirements needed to configure MySQL as a destination in the UI. You'll need the following information to configure the MySQL destination:

• Host
• Port
• Username
• Password
• Database

Known limitations

Note that MySQL documentation discusses identifiers case sensitivity using the lower_case_table_names system variable. One of their recommendations 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."

Source: MySQL docs

As a result, Airbyte MySQL destination forces all identifier (table, schema and columns) names to be lowercase.

CHANGELOG

Version	Date	Pull Request	Subject
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.