Disclaimer: This is a personal project. It is not affiliated with, endorsed by, or supported by any employer or vendor.
duckrun runs SQL in DuckDB and reads/writes Delta Lake via delta-rs — locally or on OneLake / S3 / GCS / ADLS. It's just glue: DuckDB executes · delta-rs materializes · Arrow bridges · dbt orchestrates. Two ways to use it:
connect()— a notebook helper to query and write Delta straight from SQL (this page);- a dbt adapter that materializes models as Delta tables.
Concurrent writers are first-class: every write is snapshot-pinned and fails loud rather than silently interleaving.
Install
In a Microsoft Fabric notebook, upgrade and restart the kernel (duckrun needs duckdb ≥ 2.0.0,
which is newer than the bundled stable build; it fails loud at connect() otherwise):
!pip install duckrun --upgrade
notebookutils.session.restartPython()
For the dbt adapter, install the extra instead: pip install "duckrun[dbt]".
Quickstart — OneLake in a notebook
import duckrun
# Read-only by default — explore a lakehouse safely, no chance of an accidental write.
# Use the workspace + lakehouse GUIDs (friendly names hit an upstream OneLake read bug for now).
conn = duckrun.connect("abfss://<workspace_id>@onelake.dfs.fabric.microsoft.com/<lakehouse_id>/Tables/dbo")
conn.sql("SHOW TABLES").show()
conn.sql("select status, count(*) from orders group by status").show()
conn.sql("select * from orders").df() # native DuckDB relation → pandas (.arrow(), .pl() too)
# Time travel: read an older version with delta_scan(…, version => N)
conn.sql("select * from delta_scan('.../Tables/dbo/orders', version => 0)").show()
Need to write? Opt in with read_only=False — everything is SQL:
conn = duckrun.connect("abfss://…/Tables/dbo", read_only=False)
# write Delta straight from SQL — CREATE TABLE AS routes to delta-rs
conn.sql("CREATE OR REPLACE TABLE clean_orders AS SELECT * FROM orders WHERE amount > 0")
# raw DML routes to delta-rs (insert / update / delete / alter / drop)
conn.sql("delete from clean_orders where amount = 0")
# upsert — snapshot-pinned automatically, nothing extra to pass
conn.sql("""
MERGE INTO clean_orders t USING updates s ON t.id = s.id
WHEN MATCHED THEN UPDATE SET *
WHEN NOT MATCHED THEN INSERT *
""")
conn.close()
Multiple catalogs — attach more lakehouses and read/join across them by three-part name. In
Fabric a Warehouse is just a write-locked Lakehouse, so attach it read_only=True next to a writable
one:
conn.attach("abfss://…/warehouse.Warehouse/Tables", name="warehouse", read_only=True)
conn.attach("/data/reference", name="local")
conn.sql("select * from warehouse.mart.facts f join local.dbo.lookup l on l.id = f.id").show()
Works the same against a local path, s3://, gs://, or az://. Full method map:
Connection API · API reference ·
live multi-catalog demo.
dbt adapter
duckrun is also a dbt adapter — a thin wrapper around
dbt-duckdb that adds Delta-backed table / incremental
materializations (everything else dbt-duckdb gives you is inherited). Point a profile at a lakehouse
and dbt run:
# ~/.dbt/profiles.yml
my_project:
outputs:
dev:
type: duckrun
root_path: "abfss://<workspace_id>@onelake.dfs.fabric.microsoft.com/<lakehouse_id>/Tables"
Multiple lakehouses in one project — declare extra write roots as named catalogs: and send a
model to one with the standard dbt +database: <alias> config (e.g. a Bronze/Silver/Gold medallion
across three Fabric Lakehouses). ref() and joins resolve across them:
dev:
type: duckrun
root_path: "abfss://ws@onelake.dfs.fabric.microsoft.com/LH_Silver.Lakehouse/Tables" # default
catalogs:
lh_bronze: { root_path: "abfss://ws@onelake.dfs.fabric.microsoft.com/LH_Bronze.Lakehouse/Tables" }
lh_gold: { root_path: "abfss://ws@onelake.dfs.fabric.microsoft.com/LH_Gold.Lakehouse/Tables" }
-- models/bronze/raw_events.sql → lands in LH_Bronze
{{ config(materialized='incremental', database='lh_bronze', unique_key='id') }}
select ...
Profiles, materializations, incremental strategies (merge, insert, append, delete+insert, microbatch), sources, and automatic compaction/vacuum are all in docs/dbt-adapter.md.
Debugging a model
When a model runs but the numbers are wrong, compile it with dbt and get a DuckDB relation back —
real types, lazy, read-only. Because the adapter runs DuckDB in-process, dbt only has to compile;
duckrun executes. No dbt show JSON round trip, so nothing has to guess a type per column.
from duckrun import dbt_project
p = dbt_project("dbt/", target="dev")
p.show("orders_enriched").filter("customer = 'X'").limit(100) # pushes into the delta_scan
p.sql("select * from {{ ref('stg_orders') }} where year = 2026")
# run the model one CTE at a time to find where the row count goes wrong
p.ctes("orders_enriched") # ['base', 'allocated', 'final']
p.cte("orders_enriched", "allocated").count("*")
More — CTE slicing, which is_incremental() branch you are looking at, ephemeral models, and why
the session cannot write — in docs/dbt-debug.md.
See it on real projects: aemo and coffee are
runnable starters, and parity_tests/ runs real type: duckdb projects (jaffle_shop,
sde, MRR, TechFlow, Tuva) unchanged on duckrun — their own tests included.
Building with an AI assistant
duckrun ships a guide so AI coding assistants get the adapter's defaults right (several differ from other dbt adapters). For Claude Code:
/plugin marketplace add djouallah/duckrun
/plugin install duckrun-projects@duckrun
Other assistants read the AGENTS.md at the repo root, which points to the full guide.
None of this is required to use duckrun.
Contributing
Bug reports and PRs are welcome — see CONTRIBUTING.md for the flow (branch,
PR, which CI checks actually gate) and the short list of rules.
Docs
Everything else — architecture, snapshot isolation, conformance results, benchmarks — lives on the docs site: djouallah.github.io/duckrun.
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for duckrun 0.5.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| duckrun-0.5.7.tar.gz | 298.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| duckrun-0.5.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 612.4 kB
Release files / duckrun-0.5.7.tar.gz
| Download URL | duckrun-0.5.7.tar.gz |
|---|---|
| Size | 298.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c435ea2967e564e8e8f7c17fea6525a097f96166420736e242253ec492ea1b96
|
|
BLAKE2b-256 checksum How to use checksums |
6b12924dd44536ffc3b7688da76fcf76442cfa4c5747d7ccc28c34eee7d3d157
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / duckrun-0.5.7-py3-none-any.whl
| Download URL | duckrun-0.5.7-py3-none-any.whl |
|---|---|
| Size | 313.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
133788de90e59c84f9ccad35fcdc5adc49cecbce991eac0ca5230b01142e62a0
|
|
BLAKE2b-256 checksum How to use checksums |
950f2bc04441d2c1aae7461ab9ef5b553e4bf229de927fa699a3c25283dcdf63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for duckrun 0.5.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for duckrun-0.5.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
