federate-lakehouse-catalog

Federate Google Cloud Lakehouse catalogs to remote Iceberg catalogs.

161|37|Updated Apr 2, 2026

Search Tags:#bigquery #federation #lakehouse #databricks #cross-cloud #aws-glue

Ready to run

npx skills add https://github.com/gemini-cli-extensions/data-agent-kit-starter-pack --skill federate-lakehouse-catalog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: federate-lakehouse-catalog
Source: https://github.com/gemini-cli-extensions/data-agent-kit-starter-pack/tree/main/skills/federate-lakehouse-catalog
Command: npx skills add https://github.com/gemini-cli-extensions/data-agent-kit-starter-pack --skill federate-lakehouse-catalog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Federate Google Cloud Lakehouse catalogs to remote Iceberg catalogs like Databricks Unity Catalog or AWS Glue, enabling cross-cloud data access and unified analytics without moving data.

Core Features & Use Cases

Cross-cloud federation: connect a GCP Lakehouse to remote Unity Catalog or AWS Glue Data Catalog.
Federated querying: run queries in BigQuery that join remote catalog data with local Lakehouse tables.
Secure orchestration: align region and secret management for seamless, safe federation.

Quick Start

Federate your Google Cloud Lakehouse to remote catalogs such as Databricks Unity Catalog or AWS Glue to enable federated queries.

Frequently Asked Questions about federate-lakehouse-catalog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I query remote Databricks Unity Catalog tables from BigQuery?▼

You can query remote Databricks Unity Catalog tables from BigQuery by federating your Google Cloud Lakehouse catalog to the remote Iceberg catalog. This cross-cloud federation enables unified analytics and federated querying without moving your underlying data.

How does cross-cloud lakehouse federation with AWS Glue work?▼

Cross-cloud lakehouse federation with AWS Glue connects your GCP Lakehouse to the remote AWS Glue Data Catalog. By aligning your region and Secret Manager configurations, you can run BigQuery federated queries that join remote Iceberg catalog data with local tables.

Do I need a specific GCP environment setup to federate remote Iceberg catalogs?▼

Yes, federating remote Iceberg catalogs requires a configured Google Cloud project, proper credentials, and region-aligned Secret Manager and federation catalogs. This secure orchestration ensures seamless and safe cross-cloud data access and discovery.

Can I join AWS Glue and BigQuery data without moving data to GCP?▼

Yes, you can join AWS Glue and BigQuery data without moving it to GCP. The federation capability connects your Lakehouse to the remote AWS Glue Data Catalog, enabling federated querying directly from BigQuery across supported regions.

What is the best way to unify analytics across GCP and Databricks Iceberg catalogs?▼

The best way to unify analytics across GCP and Databricks is federating your Google Cloud Lakehouse to the remote Databricks Unity Catalog. This approach provides cross-cloud data access and unified querying directly from BigQuery.

Are there regional constraints when running BigQuery federated queries on remote catalogs?▼

Yes, BigQuery federated queries on remote catalogs are subject to regional constraints. Successful cross-cloud federation requires region-aligned Secret Manager and federation catalogs configured within your Google Cloud project to ensure secure orchestration.