

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

Andre Exner

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

Chase Zieman

“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.”

Rupak Patel
"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."
First, ensure you have access to your Azure Storage Account where your table storage is located. Obtain your account name and access key from the Azure portal. This information will be needed to authenticate and access your table data.
On your local development environment, install the Azure Storage SDK and the Typesense client library for your preferred programming language. For Python, you can use `azure-data-tables` for Azure Table Storage and `typesense` for Typesense. This can be done using pip:
```sh
pip install azure-data-tables typesense
```
Write a script to connect to your Azure Table Storage using the SDK. Initialize the `TableServiceClient` with your storage account credentials and access the specific table you want to migrate data from:
```python
from azure.data.tables import TableServiceClient
connection_string = "DefaultEndpointsProtocol=https;AccountName=your_account_name;AccountKey=your_account_key;TableEndpoint=your_table_endpoint;"
table_service_client = TableServiceClient.from_connection_string(conn_str=connection_string)
table_client = table_service_client.get_table_client(table_name="your_table_name")
```
Use your connection to retrieve data from the specified table. You can use queries to filter the data as needed. For fetching all records:
```python
entities = table_client.list_entities()
data = [entity for entity in entities]
```
Prepare the data for Typesense by transforming it into a format that Typesense can index. Typesense requires data to be in JSON format with specific field requirements as defined in your Typesense schema. Create a function to perform this transformation:
```python
def transform_data(entity):
return {
"id": entity['RowKey'],
"field1": entity.get('field1', ''),
"field2": entity.get('field2', ''),
# Add more fields as needed
}
transformed_data = [transform_data(entity) for entity in data]
```
Ensure your Typesense server is running and accessible. If not already done, set up a collection in Typesense with the appropriate schema. Use the Typesense client to create the collection if it does not exist:
```python
from typesense import Client
typesense_client = Client({
'nodes': [{
'host': 'localhost', # for Typesense Cloud use xxx.a1.typesense.net
'port': '8108', # for Typesense Cloud use 443
'protocol': 'http' # for Typesense Cloud use https
}],
'api_key': 'your_typesense_api_key',
})
collection_schema = {
"name": "your_collection_name",
"fields": [
{"name": "id", "type": "string"},
{"name": "field1", "type": "string"},
{"name": "field2", "type": "string"},
# Define additional fields based on your data
]
}
try:
typesense_client.collections.create(collection_schema)
except Exception as e:
print(f"Collection already exists or error: {e}")
```
Finally, index the transformed data into your Typesense collection. Use the `typesense` client to perform the indexing:
```python
try:
typesense_client.collections['your_collection_name'].documents.import_(transformed_data)
except Exception as e:
print(f"Error indexing data: {e}")
```
By following these steps, you can move data from Azure Table Storage to Typesense without relying on third-party connectors, ensuring a streamlined and controlled data migration process.
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.
Azure Table storage, which is a service that stores non-relational structured data in the cloud and it is well known as structured NoSQL data. Azure Table storage is a service that stores structured NoSQL data in the cloud, providing a key/attribute store with a schema less design. Azure Table storage is a very popular service used to store structured NoSQL data in the cloud, providing a Key/attribute store. One can use it to store large amounts of structured, non-relational data.
Azure Table Storage's API gives access to structured data in the form of tables. The tables are composed of rows and columns, and each row represents an entity. The API provides access to the following types of data:
1. Partition Key: A partition key is a property that is used to partition the data in a table. It is used to group related entities together.
2. Row Key: A row key is a unique identifier for an entity within a partition. It is used to retrieve a specific entity from the table.
3. Properties: Properties are the columns in a table. They represent the attributes of an entity and can be of different data types such as string, integer, boolean, etc.
4. Timestamp: The timestamp is a system-generated property that represents the time when an entity was last modified.
5. ETag: The ETag is a system-generated property that represents the version of an entity. It is used to implement optimistic concurrency control.
6. Query results: The API allows querying of the data in a table based on specific criteria. The query results can be filtered, sorted, and projected to retrieve only the required data.
Overall, Azure Table Storage's API provides access to structured data that can be used for various purposes such as storing configuration data, logging, and session state management.
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: