

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”
- Install Apache Spark: You need a Spark environment because Iceberg is integrated with Spark. Download and set up Apache Spark if you haven’t already.
- Set Up Iceberg: Ensure that you have the Iceberg library available in your Spark environment. You might need to include the Iceberg connector for Spark as a dependency in your project.
- Configure AWS CLI: Make sure you have the AWS Command Line Interface (CLI) installed and configured with the necessary credentials to access your Redshift cluster and S3 buckets.
- Unload Data to S3:
Use the UNLOAD command in Redshift to export the data to an S3 bucket. This command allows you to export the result of a query to S3 in a parallelized manner.UNLOAD ('SELECT * FROM your_redshift_table')
TO 's3://yourbucket/yourdata/'
IAM_ROLE 'arn:aws:iam::0123456789012:role/YourRedshiftRole'
FORMAT AS PARQUET; - Verify Data:
Check the S3 bucket to ensure that the data has been exported correctly.
- Download Data from S3 (optional):
If you prefer to work locally, download the data from S3 to your local environment.
aws s3 cp s3://yourbucket/yourdata/ ./yourdata/ --recursive - Create an Iceberg Table:
Use Spark to create an Iceberg table. You can do this programmatically or using the Spark SQL interface.
// Using Spark Scala API
val spark = SparkSession.builder()
.appName("IcebergTableCreation")
.getOrCreate()
spark.conf.set("spark.sql.catalog.local", "org.apache.iceberg.spark.SparkCatalog")
spark.conf.set("spark.sql.catalog.local.type", "hadoop")
spark.conf.set("spark.sql.catalog.local.warehouse", "hdfs://path/to/warehouse")
// Define the schema and properties for the table
val schema = new Schema( /* your schema fields */ )
val properties = Map( /* your table properties */ )
// Create the Iceberg table
TableIdentifier tableIdentifier = TableIdentifier.of("local.db", "your_iceberg_table")
spark.catalog("local").createTable(tableIdentifier, schema, properties)
- Read Data into Spark:
Read the Parquet files from S3 or your local filesystem into a Spark DataFrame.
val df = spark.read.parquet("s3://yourbucket/yourdata/" /* or local path */)
- Write Data to Iceberg Table:
Use Spark to write the DataFrame to the Iceberg table.
df.write
.format("iceberg")
.mode("append")
.save("local.db.your_iceberg_table")
Read from Iceberg Table:
Use Spark to read the data back from the Iceberg table and verify that it matches the source data from Redshift.
val resultDF = spark.read
.format("iceberg")
.load("local.db.your_iceberg_table")
resultDF.show()
- Remove Temporary Files:
If you downloaded data to your local system, you might want to clean up the temporary files.
rm -rf ./yourdata/
- Delete Data from S3 (optional):
If you want to clean up the S3 bucket, you can delete the exported data.
aws s3 rm s3://yourbucket/yourdata/ --recursive
Notes
- Make sure you have the necessary permissions to access Redshift, S3, and the Hadoop file system where Iceberg stores metadata.
- Be aware of data types and compatibility between Redshift and Iceberg.
- Depending on the size of your data, consider the network and computation costs of transferring data between systems.
- Always test with a small subset of data before moving large datasets.
- The code examples provided are in Scala, which is commonly used with Spark, but you can also use PySpark (the Python API for Spark) or Spark SQL depending on your preference.
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.
A fully managed data warehouse service in the Amazon Web Services (AWS) cloud, Amazon Redshift is designed for storage and analysis of large-scale datasets. Redshift allows businesses to scale from a few hundred gigabytes to more than a petabyte (a million gigabytes), and utilizes ML techniques to analyze queries, offering businesses new insights from their data. Users can query and combine exabytes of data using standard SQL, and easily save their query results to their S3 data lake.
Amazon Redshift provides access to a wide range of data related to the Redshift cluster, including:
1. Cluster metadata: Information about the cluster, such as its configuration, status, and performance metrics.
2. Query execution data: Details about queries executed on the cluster, including query text, execution time, and resource usage.
3. Cluster events: Notifications about events that occur on the cluster, such as node failures or cluster scaling.
4. Cluster snapshots: Point-in-time backups of the cluster, including metadata and data files.
5. Cluster security: Information about the cluster's security configuration, including user accounts, permissions, and encryption settings.
6. Cluster logs: Detailed logs of cluster activity, including system events, query execution, and error messages.
7. Cluster performance metrics: Metrics related to the cluster's performance, such as CPU usage, disk I/O, and network traffic.
Overall, Redshift's API provides a comprehensive set of data that can be used to monitor and optimize the performance of Redshift clusters, as well as to troubleshoot issues and manage security.
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: