This release is a pre-release and may not be stable for production use.
ucmodel
Not affiliated with or endorsed by Databricks.
Reads a Databricks Unity Catalog over REST into a normalised model,
compiles source DDL into the same model, and compares two models. It needs
no SQL warehouse. ucstate and ucatlas are built on it.
Its command takes a snapshot of a catalog, a file that is written once and never edited, and reports what changed between two snapshots:
ucmodel --profile my-profile snapshot --catalog my_dev # prints snapshots/my_dev-<time>-<hash>.json
ucmodel diff snapshots/OLDER.json snapshots/NEWER.json # exits 1 when anything changed
ucmodel diff OLDER.json NEWER.json --format markdown # or json
snapshot reads every schema but information_schema, or those named with
--schema, and their lineage unless --no-lineage. Reading takes about
three API calls per table, and lineage one more per table and per column.
The file holds a hash of its contents, and diff refuses a file that was
changed after it was taken. It holds what the API returns, owners' names
included.
workspace.pymakes the REST and SQL calls. It connects with a named CLI profile or withDATABRICKS_*variables, and never with a profile nobody named.reader.pyreads the raw REST state of some schemas.normalise.pyturns that into the model: one dict per object, keyedkind:schema.name, without the catalog.compiler.pyturns source DDL into the model a shadow catalog would give, offline, for the statements it knows, and declines the rest (docs/offline.md).model.pycompares two models, hashes an object, and says what an object depends on.lineage.pyreads table and column lineage over REST.snapshot.pytakes, writes and loads snapshots, andreport.pysays what changed between two.cli.pyis theucmodelcommand.sqltext.pysplits statements, strips catalogs, compares SQL text by tokens, and quotes names and strings.samples/holds three schemas' raw REST state, so that tests need no workspace. Its docstring says how to save them again.
from ucmodel import reader
from ucmodel.normalise import normalise
from ucmodel.workspace import Workspace
ws = Workspace.connect("my-profile")
model = normalise(reader.read(ws, "ucstate_prod", reader.schemas(ws, "ucstate_prod")))
It has been tested only on a Databricks Free Edition workspace.
Metadata
Release files for ucmodel 0.1.0a1
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 | Actions |
|---|---|---|---|---|
| ucmodel-0.1.0a1.tar.gz | 60.4 kB | With provenance | Details for ucmodel-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ucmodel-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for ucmodel-0.1.0a1-py3-none-any.whl |
Total release size: 118.9 kB
Release files / ucmodel-0.1.0a1.tar.gz
| Download URL | ucmodel-0.1.0a1.tar.gz |
|---|---|
| Size | 60.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8374e4e042fb1df84c669a633c8409e9633bba2ce266ae226b4b38f22f6c088b
|
|
BLAKE2b-256 checksum How to use checksums |
5d1f26c5b34b2ecd31ba3416f5e3dba8136ceda831716bc1bd52bf68d8f033ac
|
| 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 Nov 1, 2026.
Transparency logRelease files / ucmodel-0.1.0a1-py3-none-any.whl
| Download URL | ucmodel-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 58.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5ab080f65cd8101273a8089e86c3357d6db29c52992219628fa4ec3b7eae8770
|
|
BLAKE2b-256 checksum How to use checksums |
f52e050eb817eb8173c900685e8389d1b1f6ea200352989de19edc62c6c620dd
|
| 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 Nov 1, 2026.
Transparency logSecurity for ucmodel 0.1.0a1
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 ucmodel-0.1.0a1.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 Nov 1, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.