DuckDB adapter
DuckDB runs inside the Rocky process. Use it as a warehouse, as a source, or as both at once. One adapter instance can serve discovery and execution together, because both sides read the same database.
Fields
Section titled “Fields”| Field | Type | Required | Default | Description |
|---|---|---|---|---|
path |
string | No | (in-memory) | Path to a persistent DuckDB file. Required when using the same DuckDB adapter for both discovery and execution, so the discovery side sees rows written by the warehouse side. |
Pick one. Each example is a complete adapter declaration, not a complete rocky.toml.
In-memory. DuckDB opens an in-memory database instead of a database file.
[adapter.local]type = "duckdb"Persistent file.
[adapter.local]type = "duckdb"path = "warehouse.duckdb"Authentication
Section titled “Authentication”None. DuckDB runs in-process.
See also
Section titled “See also”[adapter.NAME]— fields shared by every adapter type, including the retry policy.