---
title: "ClickHouse integrates with Lakehouse Runtime Catalog"
description: "ClickHouse 26.2 introduced a beta integration with Google's Lakehouse Runtime Catalog, enabling direct queries on Google Cloud Lakehouse Apache Iceberg tables without data movement or metadata syncing. The system communicates with Google Cloud Storage through the Iceberg REST Catalog endpoint at BigLake using Google Application Default Credentials for OAuth authentication. Users create a database using the DataLakeCatalog engine configured either with a local credentials JSON file or with explicit inline OAuth parameters. Once connected, analysts can query external Iceberg tables directly or ingest datasets into native MergeTree tables for repeated, low-latency workloads. Upcoming enhancements will add write capabilities for Iceberg tables and dedicated connection management tools inside the ClickHouse Cloud interface."
---

# ClickHouse integrates with Lakehouse Runtime Catalog

[Clickhouse](https://yomu.fyi/company/clickhouse) · Melvyn Peignon · Apr 22, 2026

**Type:** Announcement

## Summary

ClickHouse 26.2 introduced a beta integration with Google's Lakehouse Runtime Catalog, enabling direct queries on Google Cloud Lakehouse Apache Iceberg tables without data movement or metadata syncing. The system communicates with Google Cloud Storage through the Iceberg REST Catalog endpoint at BigLake using Google Application Default Credentials for OAuth authentication. Users create a database using the DataLakeCatalog engine configured either with a local credentials JSON file or with explicit inline OAuth parameters. Once connected, analysts can query external Iceberg tables directly or ingest datasets into native MergeTree tables for repeated, low-latency workloads. Upcoming enhancements will add write capabilities for Iceberg tables and dedicated connection management tools inside the ClickHouse Cloud interface.

## Context

Data teams face challenges making data accessible across distributed environments, requiring unified discovery, governance, and access control across data lakes, warehouses, and operational stores without managing proprietary connectors or metadata syncing.

## Approach / What changed

ClickHouse connects directly to Google Cloud Lakehouse Runtime Catalog via the Iceberg REST Catalog API endpoint using the DataLakeCatalog database engine. It authenticates through Google Application Default Credentials via either a credentials JSON file or explicit query settings, allowing users to query Cloud Storage tables or load them into local MergeTree tables.

## Takeaways

- ClickHouse 26.2 connects to Lakehouse Runtime Catalog using the DataLakeCatalog engine and the Iceberg REST Catalog API endpoint at biglake.googleapis.com.
- Authentication is handled natively via Google Application Default Credentials, configured either by pointing to a local credentials JSON file or passing OAuth credentials in query settings.
- Because ClickHouse does not support more than one namespace level, backticks are required around table names when querying Lakehouse catalog tables directly.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Authentication](https://yomu.fyi/topic/authentication), [Google Cloud](https://yomu.fyi/topic/gcp)

- Source: [Clickhouse](https://clickhouse.com/blog/google-lakehouse-runtime)
- Source URL: https://clickhouse.com/blog/google-lakehouse-runtime
- Ingested by Yomu: 2026-08-28T01:24:52.298Z

[Read original post](https://clickhouse.com/blog/google-lakehouse-runtime)