The Airbyte MySQL destination allows you to sync data to MySQL.
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
_airbyte_emitted_at: a timestamp representing when the event was pulled from the data source. The column type in MySQL is
_airbyte_data: a json blob representing with the event data. The column type in MySQL is
Full Refresh Sync
Incremental - Append Sync
Incremental - Deduped History
To use the MySQL destination, you'll need:
To sync data to MySQL with normalization MySQL database 8.0.0 or above
To sync data to MySQL without normalization you'll need MySQL 5.0 or above.
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.
You need a MySQL user with
CREATE, INSERT, SELECT, DROP permissions. We highly recommend creating an Airbyte-specific user for this purpose.
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.
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:
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."
As a result, Airbyte MySQL destination forces all identifier (table, schema and columns) names to be lowercase.
Add sanitized json fields in raw tables to handle quotes in column names
Switch normalization flag on so users can use normalization.
Added normalization for MySQL.
Switched to get states from destination instead of source.
Fixed a bug for message length checking.
Fixed LSEP unicode characters.
Added support for outputting messages.
Added MySQL destination.