Connecting to Iceberg

Ridge delivers AI-enabled embedded analytics and data agents so product teams can build quickly, prove value, and win the customer.

Time to read
5 min read
|
For Data Platform Admins
|
Open table format
about the connection

Overview

  • Connect to an Iceberg REST catalog and read its tables
  • Reference a table directly by warehouse.namespace.table
  • Refresh on a schedule with standard cron expressions
prerequisites

What you'll need

A few connection details link Ridge to your catalog. Collect these before you start.

Step-by-step Instructions

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 carries its own refresh schedule.

3 Select a table

Pick the table Ridge reads from the catalog, referenced as warehouse.namespace.table — the warehouse name from the connection, then the namespace, then the table.

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.

Recommendations

Best practices

A few habits keep ingestion secure and predictable.

Reference

Supported features & limitations

Help

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.