starrocks-lakehouse-integration

Configure StarRocks external catalogs to query Iceberg, Hive, and Delta tables.

14|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/ivanshamaev/de-agent-skills --skill starrocks-lakehouse-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starrocks-lakehouse-integration
Source: https://github.com/ivanshamaev/de-agent-skills/tree/main/group_skills/starrocks_group_skills/starrocks_lakehouse_integration
Command: npx skills add https://github.com/ivanshamaev/de-agent-skills --skill starrocks-lakehouse-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of integrating StarRocks with lakehouse table formats so you can query and write data across Iceberg, Hive, and Delta without unnecessary data copying.

Core Features & Use Cases

  • External catalog setup (Iceberg/Hive/Delta): Create and manage StarRocks external catalogs backed by HMS, Glue, or REST so StarRocks can access lakehouse tables.
  • Cross-catalog querying and ETL: Run single-SQL federation joins between StarRocks internal tables and external Iceberg/Hive tables, and load data via INSERT INTO / INSERT OVERWRITE.
  • Performance and correctness controls: Verify partition filter pushdown with EXPLAIN, collect external-table statistics using ANALYZE on Iceberg, and keep metadata consistent using REFRESH EXTERNAL TABLE.
  • Write-back to Iceberg (StarRocks 3.1+): Create Iceberg tables through StarRocks and insert query results back into Iceberg.
  • Use Case: You maintain raw customer events in Iceberg and clean/aggregate them in StarRocks, then write the daily gold-layer aggregates back to Iceberg for downstream consumers.

Quick Start

Use the starrocks-lakehouse-integration skill to configure an Iceberg external catalog, run a cross-catalog join query with partition predicates, and refresh external table metadata after lakehouse updates.

Frequently Asked Questions about starrocks-lakehouse-integration

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

FAQPage Schema
How do I query Iceberg and Delta Lake tables directly from StarRocks without copying data?

StarRocks queries Iceberg and Delta Lake tables by configuring a CREATE EXTERNAL CATALOG backed by Hive Metastore or AWS Glue, enabling direct data federation without moving data.

How do I set up an external catalog in StarRocks for Iceberg and Hive?

You set up an Iceberg or Hive external catalog in StarRocks using the CREATE EXTERNAL CATALOG command configured with your HMS, Glue, or REST metastore endpoint to access lakehouse tables.

Can I join StarRocks internal tables with external Iceberg tables in a single SQL query?

Yes, StarRocks supports joining internal tables with external Iceberg tables in a single SQL federation query, allowing you to load results via INSERT INTO or INSERT OVERWRITE for ETL workflows.

How do I verify partition filter pushdown is working when querying Iceberg from StarRocks?

You verify partition filter pushdown by running the EXPLAIN command on your query to ensure partition predicates are pushed down, then collect statistics using ANALYZE on external Iceberg tables.

Does StarRocks support writing data back to Iceberg tables?

Yes, StarRocks 3.1+ supports write-back to Iceberg, allowing you to create Iceberg tables through StarRocks and insert query results back into Iceberg for downstream consumers.

Why do my StarRocks queries return stale data after updating an Iceberg table?

StarRocks queries return stale data when external Iceberg table metadata is outdated; run REFRESH EXTERNAL TABLE to sync metadata and maintain consistency after lakehouse updates.