dbt-polars
A dbt adapter that runs models locally using Polars. Instead of connecting to a database, dbt-polars reads and writes files — on your local filesystem, Azure Blob Storage, AWS S3, or an Iceberg catalog.
Installation
pip install dbt-polars
Extra dependencies are required for cloud and Iceberg backends:
pip install 'dbt-polars[azure]' # Azure Blob Storage
pip install 'dbt-polars[s3]' # AWS S3
pip install 'dbt-polars[iceberg]' # Apache Iceberg (SQLite, REST, Databricks, …)
Catalogs
dbt-polars uses catalogs to define where data is stored. Each catalog maps to a storage backend. You can configure multiple catalogs in a single profile and reference them from your models.
| Catalog | Backend | Status |
|---|---|---|
local |
Local filesystem | Usable |
iceberg with SQLite |
Iceberg + SQLite metastore | Usable |
iceberg with REST + Databricks |
Iceberg REST API (Unity Catalog) | Experimental |
iceberg with other backends |
Any pyiceberg-supported backend | Experimental |
azure |
Azure Blob Storage / ADLS Gen2 | Experimental |
databricks |
Unity Catalog REST API + credential vending | Experimental |
Quick start
See the Getting started guide.
A minimal profiles.yml for local development is:
my_project:
target: dev
outputs:
dev:
type: polars
schema: dev
catalog_type: local
root: ./data
Documentation
1 maintainer
Metadata
1 maintainer
Release files for dbt-polars-catalog-s3 0.2.0
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 | |
|---|---|---|---|---|
| dbt_polars_catalog_s3-0.2.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dbt_polars_catalog_s3-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / dbt_polars_catalog_s3-0.2.0.tar.gz
| Download URL | dbt_polars_catalog_s3-0.2.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b129773e2fea6177a27c93016570ebe947b7f0a801e667837589def7b2dc3ea8
|
|
BLAKE2b-256 checksum How to use checksums |
7eb72758c28f0755a8ac800dd532b06f0553d8e023bf370074cb77f5697c70da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / dbt_polars_catalog_s3-0.2.0-py3-none-any.whl
| Download URL | dbt_polars_catalog_s3-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e1f135a3b1ff5078103f463dee2f1f914907b16cfdcc16981fb046f01162f9e
|
|
BLAKE2b-256 checksum How to use checksums |
e7cf5017a78f93f915eae30095bf62c1a4de77eb9e18a41ca0701ecd1d5d0ef4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.17 {"installer":{"name":"uv","version":"0.9.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for dbt-polars-catalog-s3 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
