

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."
Start by exporting the data from your Elasticsearch index to a JSON file. Use the Elasticsearch Scroll API for large datasets to efficiently extract records. You can execute the following curl command to retrieve data:
```
curl -X GET "http://localhost:9200/your_index/_search?scroll=1m" -H 'Content-Type: application/json' -d'
{
"size": 1000,
"query": {
"match_all": {}
}
}'
```
Continuously scroll through the data using the `_scroll_id` provided in the response until all data is exported.
Ensure that DuckDB is installed on your system. You can install it using pip:
```
pip install duckdb
```
Use Python to read the exported JSON file. You can use the `json` module to load the data into a Python dictionary or list structure. This can be done by reading the file line-by-line if the JSON is in a newline-delimited format:
```python
import json
with open('data.json') as f:
data = [json.loads(line) for line in f]
```
Transform the JSON data into a tabular format suitable for DuckDB. Flatten any nested structures into a more relational form, ensuring each document corresponds to a row with consistent columns.
Open a DuckDB connection and create a table schema that matches the structure of your transformed data. Ensure that the data types in DuckDB match those extracted from Elasticsearch:
```python
import duckdb
conn = duckdb.connect('your_database.duckdb')
conn.execute("""
CREATE TABLE your_table (
column1 TYPE,
column2 TYPE,
...
)
""")
```
Insert the transformed data into the DuckDB table. This can be done using the `executemany` method for efficiency:
```python
insert_query = "INSERT INTO your_table VALUES (?, ?, ...)"
conn.executemany(insert_query, transformed_data)
```
Finally, query the DuckDB table to verify that the data has been transferred correctly. You can run a simple SELECT statement to check a few rows:
```python
results = conn.execute("SELECT FROM your_table LIMIT 10").fetchall()
for row in results:
print(row)
```
This ensures that the data integrity is maintained and the data is accessible in DuckDB.
By following these steps, you can effectively move data from Elasticsearch to DuckDB 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.
Elasticsearch is a distributed search and analytics engine for all types of data. Elasticsearch is the central component of the ELK Stack (Elasticsearch, Logstash, and Kibana).
Elasticsearch's API provides access to a wide range of data types, including:
1. Textual data: Elasticsearch can index and search through large volumes of textual data, including documents, emails, and web pages.
2. Numeric data: Elasticsearch can store and search through numeric data, including integers, floats, and dates.
3. Geospatial data: Elasticsearch can store and search through geospatial data, including latitude and longitude coordinates.
4. Structured data: Elasticsearch can store and search through structured data, including JSON, XML, and CSV files.
5. Unstructured data: Elasticsearch can store and search through unstructured data, including images, videos, and audio files.
6. Log data: Elasticsearch can store and search through log data, including server logs, application logs, and system logs.
7. Metrics data: Elasticsearch can store and search through metrics data, including performance metrics, network metrics, and system metrics.
8. Machine learning data: Elasticsearch can store and search through machine learning data, including training data, model data, and prediction data.
Overall, Elasticsearch's API provides access to a wide range of data types, making it a powerful tool for data analysis and search.
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: