Trusted by data-driven companies
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
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
"The intake layer of Datadog’s self-serve analytics platform is largely built on Airbyte.Airbyte’s ease of use and extensibility allowed any team in the company to push their data into the platform - without assistance from the data team!"
“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.”
“We chose Airbyte for its ease of use, its pricing scalability and its absence of vendor lock-in. Having a lean team makes them our top criteria. The value of being able to scale and execute at a high level by maximizing resources is immense”
Before you start moving data, ensure that you have an Apache Iceberg environment set up and ready to receive data.
- Set Up a Hadoop/Spark Cluster: Apache Iceberg can integrate with compute engines like Spark. Make sure you have a Hadoop/Spark cluster running.
- Install Iceberg: Install Apache Iceberg on your Spark cluster. You can do this by adding Iceberg’s library to Spark’s classpath.
- Create an Iceberg Table: Define the schema and partitioning strategy for your Iceberg table, and create the table using Spark SQL or the Iceberg API.
- Query Data: Write a SQL query to select the data you want to export from Snowflake.
- Export to CSV/JSON/Parquet: Use Snowflake’s data unloading capabilities to export the data into a file format that is compatible with Apache Iceberg, such as CSV, JSON, or Parquet. This can be done using the COPY INTO <location> command in Snowflake.
- Store the Data: Store the exported data files in a location accessible to your Spark cluster, such as Amazon S3, HDFS, or a local filesystem.
Depending on the format you’ve chosen to export data from Snowflake, you may need to transform it to match the schema of your Iceberg table.
- Read Data into Spark: Use Spark to read the data files into a DataFrame.
- Transform Data: Apply any necessary transformations to the DataFrame to match the schema and partitioning strategy of your Iceberg table.
- Write Data to Parquet (If Needed): If you’ve exported data in CSV or JSON format, convert it to Parquet, which is more efficient for Iceberg.
Step 4: Load Data into Apache Iceberg
- Write DataFrame to Iceberg: Use Spark’s DataFrameWriter API to write the DataFrame to the Iceberg table.
df.write
.format("iceberg")
.mode("append") // Use "overwrite" if you want to replace existing data
.save("path_to_your_iceberg_table")
- Refresh Table: After loading, refresh the Iceberg table to ensure that the metadata is updated and your data is visible.
- Query Iceberg Table: Use Spark SQL to query the Iceberg table and validate that the data has been transferred correctly.
- Check Data Integrity: Compare the results of similar queries run on Snowflake and Iceberg to ensure data integrity.
- Remove Temporary Files: If you created any temporary files or directories during the data transfer process, clean them up to prevent storage waste.
- Monitor Performance: Keep an eye on the performance of your Spark jobs and the Iceberg table. Adjust configurations as needed for optimal performance.
Once you have successfully moved data manually, you might want to automate the process for recurring data transfers.
- Scripting: Write scripts to automate the export from Snowflake, transformation, and loading into Iceberg.
- Scheduling: Use a job scheduler like Apache Airflow, Oozie, or a cloud service equivalent to schedule the data transfer jobs.
Notes:
- Ensure that you have the necessary permissions to access both Snowflake and the storage used by Apache Iceberg.
- Be mindful of the data volume and network throughput, as transferring large datasets can be time-consuming and may incur costs.
- Consider incremental data loads if you are dealing with frequently updated datasets to optimize the data transfer process.
- Always test your data migration process with a subset of data before moving the entire dataset.
By following these steps, you can manually move data from Snowflake 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.
Snowflake Data Cloud is a cloud-based data warehousing and analytics platform that allows organizations to store, manage, and analyze large amounts of data in a secure and scalable manner. It provides a single, integrated platform for data storage, processing, and analysis, eliminating the need for multiple tools and systems. Snowflake Data Cloud is built on a unique architecture that separates compute and storage, allowing users to scale up or down as needed without affecting performance. It also offers a range of features such as data sharing, data governance, and machine learning capabilities, making it a comprehensive solution for modern data management and analytics.
Snowflake Data Cloud provides access to a wide range of data types, including:
1. Structured Data: This includes data that is organized in a specific format, such as tables, columns, and rows. Examples of structured data include customer information, financial data, and inventory records.
2. Semi-Structured Data: This type of data is partially organized and may not fit into a traditional relational database structure. Examples of semi-structured data include JSON, XML, and CSV files.
3. Unstructured Data: This includes data that does not have a specific format or organization, such as text documents, images, and videos.
4. Time-Series Data: This type of data is organized based on time stamps and is commonly used in industries such as finance, healthcare, and manufacturing.
5. Geospatial Data: This includes data that is related to geographic locations, such as maps, GPS coordinates, and satellite imagery.
6. Machine Learning Data: This type of data is used to train machine learning models and includes features and labels that are used to predict outcomes.
Overall, Snowflake Data Cloud provides access to a wide range of data types, making it a versatile tool for data analysis and 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:
