.duckdb artifact identified by
an opaque file reference rather than a host, port, username, password, or
browser-supplied filesystem path.
Connection fields
The destination reference must differ from any DuckDB source reference used
by the same pipeline. MantrixFlow rejects same-artifact source and destination
configurations before dispatch.
Create the destination connection
- Open Connections and click + New Connection.
- Set the role to Destination.
- Choose DuckDB.
- Enter a connection name and an existing managed destination reference.
- Keep Default Schema as
mainunless the destination contract specifies another schema. - Click Test Connection.
- Save only after the test succeeds.
/tmp/..., ../..., file://..., or a SQLAlchemy
connection URL. Only trusted runtime services may materialize an artifact to a
worker-local path.
Destination behavior
The ELT runtime resolves the opaque reference under a persistent server-owned artifact root and never falls back to an in-memory database. Public delivery uses direct DuckDBON CONFLICT Upsert into a pre-existing table with a primary
key. It does not create or alter destination tables and does not add _dlt_*
tables or columns.
Concurrency and version safety
The runtime holds one non-blocking, process-safe writer lease per artifact. Concurrent writers are rejected, each run checks the expected artifact version, and a successful delivery atomically advances a sidecar version. Interrupted version temp files are recoverable without deleting the.duckdb artifact.
This is optimistic version tracking for the managed mutable artifact, not an
immutable backup or rollback service.
Troubleshooting
See DuckDB source for read-only source,
discovery, preview, and sync-mode guidance.