.avif)
How Ridge works with Iceberg
What you can do
- Connect to an Iceberg REST catalog and read its tables
- Reference a table directly, or shape it with a custom SQL query
- Refresh on a schedule with standard cron expressions
What you'll need
A few connection details link Ridge to your catalog. Collect these before you start.
Set up the connection
1 Create a Connection
On the Data page, click New Connection and choose Iceberg as the type. Enter the credentials you gathered, then save.
- Endpoint and Warehouse Name
- Token — a catalog bearer token
2 Create a Dataset
Back on the Data page, click New, select source Connection, and pick the Iceberg connection you just created. A Data Set points at a specific table and can carry its own query and refresh schedule.
3 Select a table, or write a query
Choose how Ridge reads from the catalog. A direct table reference is simplest; custom SQL lets you filter and aggregate at the source.
4 Schedule ingestion
Set an ingestion schedule with standard cron syntax, then save. Ridge reads from the catalog and stores the results, ready for analysis.
Best practices
A few habits keep ingestion secure and predictable.
Supported features & limitations
- Reads Iceberg tables via the REST catalog
- Validates the connection before ingestion with a
SELECT 1probe - Uses the DuckDB
icebergandhttpfsextensions
- REST catalog only — connects to an Iceberg REST catalog.
- Bearer-token auth only — other catalog auth methods are not supported.
Troubleshooting
Most connection issues fall into four buckets. Expand the one that matches your error.
Invalid credentials
401, "unauthorized", "invalid token"
Your catalog token is wrong or expired. Re-enter it.
Insufficient permissions
403, "forbidden"
The token lacks rights. Grant read access on the namespace or table.
Resource not found
404, "NoSuchNamespace", "NoSuchTable", "does not exist"
The namespace or table name is wrong. Fix it.
Network unreachable
"could not resolve host", "could not establish connection", "timed out", "connection refused"
The endpoint is unreachable. Check the endpoint URL and your egress allowlist.
