

Building your pipeline or Using Airbyte
Airbyte is the only open source solution empowering data teams to meet all their growing custom business demands in the new AI era.
- Inconsistent and inaccurate data
- Laborious and expensive
- Brittle and inflexible
- Reliable and accurate
- Extensible and scalable for all your needs
- Deployed and governed your way
Start syncing with Airbyte in 3 easy steps within 10 minutes



Take a virtual tour
Demo video of Airbyte Cloud
Demo video of AI Connector Builder
Setup Complexities simplified!
Simple & Easy to use Interface
Airbyte is built to get out of your way. Our clean, modern interface walks you through setup, so you can go from zero to sync in minutes—without deep technical expertise.
Guided Tour: Assisting you in building connections
Whether you’re setting up your first connection or managing complex syncs, Airbyte’s UI and documentation help you move with confidence. No guesswork. Just clarity.
Airbyte AI Assistant that will act as your sidekick in building your data pipelines in Minutes
Airbyte’s built-in assistant helps you choose sources, set destinations, and configure syncs quickly. It’s like having a data engineer on call—without the overhead.
What sets Airbyte Apart
Modern GenAI Workflows
Move Large Volumes, Fast
An Extensible Open-Source Standard
Full Control & Security
Fully Featured & Integrated
Enterprise Support with SLAs
What our users say


"For TUI Musement, Airbyte cut development time in half and enabled dynamic customer experiences."


“Airbyte helped us accelerate our progress by years, compared to our competitors. We don’t need to worry about connectors and focus on creating value for our users instead of building infrastructure. That’s priceless. The time and energy saved allows us to disrupt and grow faster.”

"With Airbyte, we could just push a few buttons, allow API access, and bring all the data into Google BigQuery. By blending all the different marketing data sources, we can gain valuable insights."
Begin by ensuring your MySQL database is ready for data export. This involves identifying the tables you wish to export and ensuring that the data is in a consistent state. You may need to temporarily disable write operations or use a consistent snapshot to avoid data inconsistency during the export process.
Utilize the MySQL `SELECT INTO OUTFILE` command to export your data into CSV format. This command allows you to specify the directory and file name, as well as options for field and line terminators. For example:
```sql
SELECT INTO OUTFILE '/path/to/yourfile.csv'
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n'
FROM your_table;
```
Once you have your CSV files, you need to move them to the Hadoop Distributed File System (HDFS), where Apache Iceberg can access them. Use the `hdfs dfs -put` command to upload the CSV files to HDFS:
```bash
hdfs dfs -put /local/path/to/yourfile.csv /hdfs/path/
```
Set up a Hive table that will serve as an interface to Apache Iceberg. You need to define the schema of the table to match the structure of your CSV data. Use Hive's DDL commands to create an Iceberg table:
```sql
CREATE TABLE iceberg_table (
column1 INT,
column2 STRING,
...
)
STORED BY 'org.apache.iceberg.mr.hive.HiveIcebergStorageHandler'
TBLPROPERTIES ('iceberg.catalog'='hive');
```
Use Hive's `LOAD DATA` command to load the CSV data into the Hive table. This step transfers the CSV data into the Iceberg table format:
```sql
LOAD DATA INPATH '/hdfs/path/to/yourfile.csv' INTO TABLE iceberg_table;
```
After loading the data, verify that the data has been accurately transferred by performing a few queries on the Iceberg table. This ensures that all data has been correctly imported and is accessible:
```sql
SELECT FROM iceberg_table LIMIT 10;
```
Finally, optimize the Iceberg table for better performance and storage efficiency. You can perform compaction and remove any redundant snapshots or files. Use Iceberg's maintenance commands to optimize the structure:
```sql
CALL iceberg_table.optimize();
```
By following these steps, you can successfully move data from MySQL to Apache Iceberg without relying on third-party connectors or integrations.
FAQs
What is ETL?
ETL, an acronym for Extract, Transform, Load, is a vital data integration process. It involves extracting data from diverse sources, transforming it into a usable format, and loading it into a database, data warehouse or data lake. This process enables meaningful data analysis, enhancing business intelligence.
MySQL is an SQL (Structured Query Language)-based open-source database management system. An application with many uses, it offers a variety of products, from free MySQL downloads of the most recent iteration to support packages with full service support at the enterprise level. The MySQL server, while most often used as a web database, also supports e-commerce and data warehousing applications and more.
MySQL provides access to a wide range of data types, including:
1. Numeric data types: These include integers, decimals, and floating-point numbers.
2. String data types: These include character strings, binary strings, and text strings.
3. Date and time data types: These include date, time, datetime, and timestamp.
4. Boolean data types: These include true/false or yes/no values.
5. Spatial data types: These include points, lines, polygons, and other geometric shapes.
6. Large object data types: These include binary large objects (BLOBs) and character large objects (CLOBs).
7. Collection data types: These include arrays, sets, and maps.
8. User-defined data types: These are custom data types created by the user.
Overall, MySQL's API provides access to a wide range of data types, making it a versatile tool for managing and manipulating data in a variety of applications.
What is ELT?
ELT, standing for Extract, Load, Transform, is a modern take on the traditional ETL data integration process. In ELT, data is first extracted from various sources, loaded directly into a data warehouse, and then transformed. This approach enhances data processing speed, analytical flexibility and autonomy.
Difference between ETL and ELT?
ETL and ELT are critical data integration strategies with key differences. ETL (Extract, Transform, Load) transforms data before loading, ideal for structured data. In contrast, ELT (Extract, Load, Transform) loads data before transformation, perfect for processing large, diverse data sets in modern data warehouses. ELT is becoming the new standard as it offers a lot more flexibility and autonomy to data analysts.
What should you do next?
Hope you enjoyed the reading. Here are the 3 ways we can help you in your data journey: