ClickHouse at Google Cloud Next '26

ClickhouseClickHouseApr 27, 2026

Source: Clickhouse
Published: Apr 27, 2026
Added to Yomu: Aug 28, 2026

Announcement

Summary

ClickHouse announced several product updates and integrations designed to deepen native compatibility with Google Cloud. Migration of ClickHouse Cloud to Google Axion ARM-based processors demonstrated a 30 to 55 percent query speed increase and reduced data load times from 64 to 26 seconds on ClickBench benchmarks. An integration with Google Lakehouse Runtime Catalog enables querying Iceberg tables on Google Cloud Storage via the DataLakeCatalog engine without data movement. Furthermore, Bring Your Own Cloud reached general availability on Google Cloud Marketplace, and ClickPipes added an unordered mode using Pub/Sub notifications for GCS ingestion. Google Antigravity integrated ClickHouse through an MCP server to translate natural language into SQL and generate interactive React charts.

Context

Enterprise workloads and data pipelines on Google Cloud require high-performance analytics, strict data residency compliance, and seamless ingestion without manual ETL or file ordering constraints on storage buckets.

Approach / What changed

ClickHouse introduced deployments on Google Axion ARM processors, direct Iceberg querying via Lakehouse Runtime Catalog, Bring Your Own Cloud availability on GCP Marketplace, an MCP server integration for Google Antigravity, and unordered GCS ingestion in ClickPipes using OBJECT_FINALIZE Pub/Sub notifications.

Takeaways

In March 2026 ClickBench benchmarks, ClickHouse Cloud running on Google Axion processors improved query performance by 30 to 55 percent and decreased data loading time from 64 seconds to 26 seconds.
The Lakehouse Runtime Catalog integration allows ClickHouse to query Iceberg tables in Google Cloud Storage directly using the DataLakeCatalog engine with catalog_type set to biglake.
ClickPipes unordered mode replaces 30-second bucket polling with GCS OBJECT_FINALIZE Pub/Sub notifications and uses a metadata store to provide exactly-once processing for out-of-order files.

Read original post

ClickHouse at Google Cloud Next '26

ClickhouseClickHouseApr 27, 2026

Source: Clickhouse
Published: Apr 27, 2026
Added to Yomu: Aug 28, 2026

Announcement

Summary

Context

Approach / What changed

Takeaways

In March 2026 ClickBench benchmarks, ClickHouse Cloud running on Google Axion processors improved query performance by 30 to 55 percent and decreased data loading time from 64 seconds to 26 seconds.
The Lakehouse Runtime Catalog integration allows ClickHouse to query Iceberg tables in Google Cloud Storage directly using the DataLakeCatalog engine with catalog_type set to biglake.
ClickPipes unordered mode replaces 30-second bucket polling with GCS OBJECT_FINALIZE Pub/Sub notifications and uses a metadata store to provide exactly-once processing for out-of-order files.

Read original post

Related reading

Clickhouse · Apr 21, 2026
ClickHouse expands strategic collaboration with Google Cloud, bringing deeper integration, cloud flexibility, and next-generation performance
ClickHouse announced an expanded strategic collaboration with Google Cloud introducing four core architectural milestones. First, native integration with Google Cloud Lakehouse allows direct sub-second queries across data lakes and ClickHouse deployments without ETL pipelines or data duplication. Second, the Bring Your Own Cloud deployment model lets organizations run managed ClickHouse Cloud inside their own Google Cloud Virtual Private Cloud to retain data sovereignty and network controls. Third, ClickHouse Cloud is migrating automatically to Google's custom Arm-based Axion processors, boosting query throughput and cost efficiency for analytical workloads without requiring application changes. Finally, a new ClickHouse MCP server integration connects ClickHouse with Google Antigravity to enhance developer and analyst workflows.
Tanya Bragin
Clickhouse · Apr 22, 2026
ClickHouse integrates with Lakehouse Runtime Catalog
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.
Melvyn Peignon
Clickhouse · Apr 22, 2026
Using the ClickHouse MCP server with Google Antigravity
Google Antigravity integrates with the ClickHouse Model Context Protocol server to provide agent-driven analytics within the developer environment. Users install the server from Antigravity's MCP Store panel and authenticate via OAuth, granting the agent read-only access to organizations, services, databases, and tables according to account permissions. When prompted with natural language, the agent uses tools like get_services_list and list_tables to inspect schemas, translating user requests into functional ClickHouse SQL executed through the run_select_query tool. Antigravity can also generate interactive React charts as Artifacts, test UI interactions with screen recordings and screenshots in an integrated browser, and refine queries based on visual area comments. This setup allows engineers and analysts to explore datasets interactively without switching between external database clients and ticketing workflows.
Dustin Healy
Clickhouse · Mar 16, 2026
Unordered mode for GCS ClickPipes is now available
ClickHouse Cloud has added unordered mode to its Google Cloud Storage (GCS) ClickPipes connector, enabling continuous data ingestion regardless of file naming or arrival sequence. Standard GCS ClickPipes rely on polling every 30 seconds and require files to arrive in strict lexicographical order, which causes out-of-order data and backfills to be ignored. Unordered mode replaces polling by consuming OBJECT_FINALIZE notifications from Google Cloud Pub/Sub whenever objects land in a bucket. State tracking is managed through a metadata store, and the connector automatically reprocesses batches upon failure while maintaining exactly-once insertion guarantees. Setup requires configuring a Pub/Sub topic and bucket notifications via tools like gcloud, followed by configuring the ClickPipe via the console or Terraform provider.
Marta Paes