New: Cookbooks and AI ExplanationsStep-by-Step recipes to solve problems connected to Roadmaps and Cheat Sheets. Need more details? Use AI buttons for structured and simple explanations with concrete examples throughout the whole platform.Take a look
Every Iceberg tutorial assumes you already have a Spark cluster running. What if you just want to peek at one table?
What you'll have at the end
A Python script that connects to your team's existing catalog, loads one named Iceberg table pinned to a specific snapshot, and returns a filtered slice of its rows as a dataframe with that snapshot ID printed alongside the row count.
You need
Working read access to an Iceberg table through your organization's catalog, meaning connection details or credentials someone on your platform team can hand you, plus that table's full name.
Not covered
Writing, updating, or deleting rows in the table, and standing up a brand new catalog from scratch.
A bad write on a lakehouse table, rolled back with time travel
once you can read a table's current snapshot on demand, rolling back to an earlier one after a bad write is the natural next question, and it deserves its own care around commit history
Pick a catalog so Spark and Trino can query the same lakehouse table
when more than one engine needs to see the same table, which catalog you connect through stops being a one-line choice and becomes a decision the whole team has to agree on
Checked 26 Aug 2026
Part of the Data Lakehouse cookbook