Apache Iceberg integration
Your models, in Apache Iceberg.
A built-in ingestr destination: load modelled tables into Apache Iceberg.
name: out.apache_iceberg
type: ingestr
parameters:
source_connection: postgres
source_table: analytics.daily_revenue
destination: apache_iceberg$ bruin run assets/out/apache_iceberg.asset.yml
- extract · postgres analytics.daily_revenue
- load · Apache Icebergreplace
Delivered to Apache Iceberg.
How it connects
Connected in three steps.
Apache Iceberg is an open table format for large analytic datasets.
- 01
Add a Apache Iceberg connection.
- 02
Point an ingestion asset at Apache Iceberg as its destination.
- 03
Bruin loads it on your schedule and checks every load.
Connection parameters
- bucket
- bucket name for the bucket/prefix shorthand, producing s3://bucket/prefix (or gs://bucket/prefix with storage=gcs).
- warehouse
- advanced override for the Iceberg warehouse location, such as s3://bucket/warehouse.
- warehousepath
- local warehouse path alias for non-S3 catalog setups.
The platform
Part of the Bruin platform.
Data in, ready for everything downstream: the models, the checks, the lineage and the AI layer.
01 · Move
02 · Model & govern
03 · Use
Frequently asked
Questions about Apache Iceberg.
Does Bruin have a built-in Apache Iceberg integration?
Yes. Built-in ingestr destination.
How fresh is the data?
As fresh as your schedule. Incremental loads append, merge or replace a time window, every few minutes if you like.
Do we need Bruin Cloud?
No. The Bruin CLI and ingestr run locally, in CI or in your own orchestrator. Bruin Cloud adds scheduling, lineage, alerts and the AI data analyst on top.
Ready to connect Apache Iceberg?
$100 in credits and 50 AI tasks. No credit card.
A demo walks through your own data.