tablevalidator-databricks
A widget-driven Databricks notebook UI for table-validator
- generates a notebook with
dbutils.widgetsfor picking source/target tables and validation checks, so you can run a comparison without writing any Python.
This package contains no validation logic of its own. It only writes a
notebook file whose cells call directly into table-validator's own
validate_tables() API - the exact same engine the CLI (tablevalidator)
and the notebook-native Python API already use.
Install
pip install tablevalidator-databricks
Installing this package also installs table-validator (a dependency), so
there's nothing else to install separately.
Usage
tablevalidator-databricks info
Prints a full usage guide - the steps, the three modes, what each check group actually does, schema-wide sweeps, the cascading-dropdown caveat, manual overrides, and version pinning. Start here if you're new to it.
tablevalidator-databricks init
Writes ./TableValidator.py - a ready-to-use Databricks notebook. Options:
tablevalidator-databricks init --output MyValidation.py --mode full
--mode basic- only the check-group Yes/No dropdowns and table pickers.--mode full(default) - also shows optional filter widgets (only/ ignore columns, row filter, primary key). Every check defaults to "Yes".--mode schema- same widgets asbasic, but the Row checks default to "No" - a lightweight schema-shape-only comparison out of the box (still changeable per-run).
Note on the check groups: "Catalog & Schema" only verifies that catalogs/schemas/tables exist and match by name - it produces no per-table PASS/FAIL by itself, so running it alone reports every table as
SKIPPED. The per-table verdict comes from the Column checks (names, types, nullability, statistics) and Row checks (row counts, row-level data).
Then, in your Databricks workspace: Workspace -> Import, format
"Source", and select the generated file. Databricks recognizes the
# Databricks notebook source header and # COMMAND ---------- cell
markers and opens it as a real notebook.
What the generated notebook does
- Installs
table-validator(%pip install table-validator). - Queries Unity Catalog (
SHOW CATALOGS/SHOW SCHEMAS IN .../SHOW TABLES IN ...via the notebook's own ambient Spark session) to populate Source/Target Catalog, Schema, and Table dropdowns. - Shows a Yes/No dropdown per check group (Catalog & Schema / Column /
Row - the three independently-selectable check groups the engine
actually supports) plus, in
fullmode, optional text widgets for column filtering, a row filter, and a primary key. - On run, reads every widget and calls
validate_tables(source, target, enabled_validations=..., ...), then prints a summary and displays the Table Validation sheet.
Cascading dropdowns: Databricks widgets don't auto-refresh when an upstream selection changes. After changing Source/Target Catalog or Schema, re-run the notebook's "Create / refresh widgets" cell once to repopulate the dropdowns below it before running the rest of the notebook. This is a Databricks widget limitation, not a bug in the generated notebook. If you skip this and run validation anyway with a stale Schema/ Table selection, the notebook fails with a clear error telling you which cell to re-run, rather than silently comparing the wrong table.
Can't find a name in a dropdown? Every Catalog/Schema/Table dropdown has a matching "(manual override)" text widget next to it. Type the exact name there and it's used instead of the dropdown - useful if something isn't showing up (a permissions lag, sort order, anything). It's used as-is, not checked against the live catalog listing. Leave every override blank to just use the dropdowns as normal.
Validate every table in a schema, not just one: pick
"(all tables in schema)" as the Table dropdown (Source and/or Target
independently) to compare every identically-named table in that schema in
one run - the same schema-wide sweep validate_tables() itself supports.
A primary key can't be set in this mode (leave the Primary Key widget
blank). Comparing every schema in a catalog isn't supported yet - Schema
must be a specific choice, even when Table is left as "(all ... in ...)".
Why a separate package
table-validator stays focused on the actual comparison engine (CLI +
notebook API + report generation). This package is purely a Databricks-
specific UI layer on top of it - keeping the two independently versioned
and installable means CLI-only or code-only users never need Databricks-
specific tooling pulled in, and this package can add more Databricks UX
(e.g. richer widgets) without touching the core engine at all.
Development
pip install -e ".[dev]"
pytest
License
MIT - see the table-validator repository's LICENSE.
Metadata
Release files for tablevalidator-databricks 0.1.8
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 |
|---|---|---|---|---|
| tablevalidator_databricks-0.1.8.tar.gz | 23.4 kB | With provenance | Details for tablevalidator_databricks-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tablevalidator_databricks-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for tablevalidator_databricks-0.1.8-py3-none-any.whl |
Total release size: 40.2 kB
Release files / tablevalidator_databricks-0.1.8.tar.gz
| Download URL | tablevalidator_databricks-0.1.8.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32f2d4e76947fbf0b58d73d50b3c677ed6b78f234c29bb0ef102555a19680c4f
|
|
BLAKE2b-256 checksum How to use checksums |
1c93daf3719c668da88ca21f981418e3ce3d98de9d05aac473ed6b61cc7f86cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 11, 2026.
Transparency logRelease files / tablevalidator_databricks-0.1.8-py3-none-any.whl
| Download URL | tablevalidator_databricks-0.1.8-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6995c900884c9372f7ce19af9b14122b416d68a95e15c982bb3c281566bf098
|
|
BLAKE2b-256 checksum How to use checksums |
0bb113cc266124039fb2e50f898d3bc3365f7c35ee483e6eba6c2fb96489f2a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 11, 2026.
Transparency logSecurity for tablevalidator-databricks 0.1.8
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
Both files in this release have been uploaded with provenance metadata.
Attestation for tablevalidator_databricks-0.1.8.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 Sep 11, 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.