Bruin CLI

Appearance

Lakehouse Support beta ​

WARNING

Lakehouse support is currently in beta. APIs and configuration may change in future releases.

Bring lakehouse tables directly into your Bruin pipelines. Query Iceberg and DuckLake data on cloud object storage with a catalog-backed metadata layer, all from the same workflows you already use. This page summarizes supported engines, catalogs, and storage backends.

Engines and formats ​

DuckDB and Trino are the engines Bruin supports. In each section, you can discover the lakehouse format + catalog/storage combination supported by Bruin. Visit DuckDB or Trino for Bruin configurations.

DuckDB ↗ ​

Iceberg and DuckLake format are natively supported in Bruin.

DuckLake ​

DuckLake uses a DuckDB, SQLite, or Postgres catalog. The table shows supported storage + catalog combinations. For more guidance, see DuckLake's choosing a catalog database.

CatalogS3
DuckDB
SQLite
Postgres
MySQLPlanned

Iceberg ​

Iceberg uses the AWS Glue Data Catalog (AWS Glue Data Catalog). The table shows supported storage + catalog combinations.

CatalogS3
Glue

Trino ↗ ​

Trino supports lakehouse access via the Iceberg connector with Glue and Nessie catalogs. Detailed setup guides are coming soon. Check out Trino for Bruin configuration.

CatalogS3
Glue
Nessie

What is a Lakehouse? ​

A lakehouse combines the scalability of data lakes with the reliability of data warehouses. Data is stored in open formats on object storage (S3, GCS, Azure Blob) while metadata catalogs track schema, partitions, and table history.

Quick Start ​

Let's add a DuckLake lakehouse configuration to your DuckDB connection (DuckDB catalog + S3 storage):

yaml
connections:
  duckdb:
    - name: "analytics"
      path: "./path/to/duckdb.db"
      lakehouse:
        format: ducklake
        catalog:
          type: duckdb
          path: "metadata.ducklake"
        storage:
          type: s3
          path: "s3://my-ducklake-warehouse/path"
          region: "us-east-1"
          auth:
            access_key: "AKIA..."
            secret_key: "..."

Then query your Iceberg tables (defaults to the main schema):

Bruin-sql
/* @Bruin
name: lakehouse_users
type: duckdb.sql
connection: analytics
@Bruin */


SELECT * FROM users;

See the engine-specific pages DuckDB or Trino for detailed configuration options.