sql-federated-queries

Create Kafka/Iceberg catalogs to federate Oxla queries across external sources.

6|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/redpanda-data/skills --skill sql-federated-queries
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-federated-queries
Source: https://github.com/redpanda-data/skills/tree/main/skills/sql-federated-queries
Command: npx skills add https://github.com/redpanda-data/skills --skill sql-federated-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Oxla users need to query data that lives outside native Oxla tables—Kafka/Redpanda sources, Iceberg catalogs, and object storage—without ETL. This skill provides SQL-based access to external data via named catalogs and external data pathways, enabling joins and analytics across heterogeneous data stores.

Core Features & Use Cases

  • Federated querying across Kafka/Redpanda topics and Iceberg tables from a single SQL interface.
  • Create and manage KAFKA/REDPANDA and ICEBERG catalogs to connect to external data sources.
  • Use COPY FROM/TO and icebergs/rest catalogs to read and write external data alongside native Oxla tables.
  • Real-world scenario: join a Kafka source with an Iceberg table to derive customer insights without loading data into Oxla.

Quick Start

Run a basic federated query by connecting a Kafka catalog and an Iceberg catalog, then query a topic through a catalog=>table syntax.

Frequently Asked Questions about sql-federated-queries

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

FAQPage Schema
How do I query external Kafka topics and Iceberg tables using SQL without ETL?

Federated SQL queries enable you to query external Kafka topics and Iceberg tables without ETL. By creating named catalogs in Oxla, you can join external data with native tables directly through a single SQL interface.

Can I join Kafka streaming data with an Iceberg table in a single SQL query?

Yes, you can join Kafka streaming data with an Iceberg table in a single SQL query. This federated querying capability allows you to derive cross-source customer insights by connecting both a Kafka catalog and an Iceberg catalog.

How do I create and manage a Kafka or Iceberg catalog for cross-source data access?

You create and manage external data connections using CREATE KAFKA CATALOG and CREATE ICEBERG CATALOG statements. These named catalogs enable cross-source data access, supporting REFRESH, ALTER, and per-topic options with safety checks for schema decoding.

Does Oxla support COPY FROM and COPY TO operations against S3, GCS, and Azure object storage?

Yes, Oxla supports COPY FROM and COPY TO operations against S3, GCS, and Azure-based object storage. This allows you to read and write external data alongside native Oxla tables through federated SQL pathways.

What are the prerequisites for federating Oxla with external Kafka and Iceberg sources?

Federating Oxla with external Kafka and Iceberg sources requires setting up named catalogs with proper authentication. The system includes safety checks for authentication and schema decoding to ensure secure cross-source data access.

Are there limitations when performing cross-source federated queries on Kafka and Iceberg data?

Cross-source federated queries require per-topic and per-catalog options configuration, including schema decoding and authentication safety checks. Complex joins between Kafka streams and Iceberg tables may need careful catalog management to ensure accurate analytics.