Dremio
Connect a Dremio lakehouse query engine to Lakehousecat over its native Arrow Flight endpoint — no ODBC or JDBC driver required.
Connection Fields
| Field | Required | Description |
|---|---|---|
| Connection URI | Yes | Format: dremio://user:password@host:32010. Use dremio+tls:// for a TLS-enabled cluster. Example: dremio://lhc_admin:password@dremio-host:32010 |
Prerequisites
- Admin or Builder role in Lakehousecat
- A Dremio user with read access to the spaces/tables you want to expose
- Network connectivity from the Lakehousecat backend to Dremio's Flight port (32010) — the web UI/REST port (9047) will not accept this connection
Notes
- The connection URI has no database or path segment — Dremio spaces and schemas are addressed per query, not in the connection string.
- v1 scope is full load only. Incremental load requires explicitly configured merge keys in the Filters tab once available — Dremio is a query engine without its own primary keys, so there is no automatic detection.
- A connection to the wrong host or port typically surfaces as a generic write error rather than an obvious "connection refused" — double-check host and port (32010, not 9047) first.
Supported Features
| Feature | Supported |
|---|---|
| Full Load | ✅ |
| Incremental Load | ❌ (planned) |
| Schema Filter | ✅ |
| Column Filter | ✅ |
| Row Filter | ❌ |
| SSH Tunnel | ❌ |
Next Steps
After creating the datasource, go to the Operations tab to trigger semantic extraction.