Skip to main content
ReferenceApplies to: Unified engine deployments
Live table examples use Hub’s Lakekeeper Iceberg REST catalog and MinIO storage. Hub runs separately from the engine through Docker Compose. Follow Hub setup to start the services, generate the data, and connect the catalog.

TPC-DS SF1

Run the full SF1 command in Hub setup to generate all rows for the seven tables below. Each generation uses a separate namespace. Use that namespace in your SQL client and check that the tables exist. Source tables remain separate from the write lab. Examples show sample tables as demo.tpcds.item, demo.tpcds.store_sales, and so on. Replace these names with the catalog and namespace of your TPC-DS SF1 dataset. This keeps the SQL readable when the dataset changes.

Useful relationships

Sales can contain null foreign keys. Choose an outer join when those sales should remain in the result. An inner join keeps only matching rows.

Write lab

Create a private namespace and an items table containing item keys 1–20 from SF1. Its columns are i_item_sk, i_item_id, i_category, and price (DOUBLE). Published write examples target this namespace. Examples that recreate a table explain that behavior before the SQL. Remove only your private lab objects when you finish; keep the source SF1 tables.
Run related statements in order in the same SQL session and stop at the first failure. Inspect each statement’s result.
Last modified on November 4, 2026