ODCS contracts
BetaImport, export and validate Open Data Contract Standard v3.1 contracts, and check them for schema drift with Catalog.
Use the open standard for data contracts, and let Nistor check that reality still matches them.
What Nistor collects
- Contracts written in ODCS v3.1, validated and imported as Data Trust contracts.
- Drift, with Catalog (Enterprise): missing or extra columns and type mismatches between a contract and the live columns in the Catalog. Drift covers the schema only.
- Quality rules in a contract become checks with Data quality (Enterprise).
Contracts can also be exported back to ODCS.
Set it up
This integration is in beta and on by default; an operator can turn it off. Contracts reach Nistor in one of two ways: pushed from CI with nistor odcs sync, or uploaded in Nistor. Nistor does not pull them from your repository itself. The README in the repository explains both.
The setup guide comes with the docs, soon.
Other integrations
GitLab
PreviewRepositories and deploy provenance on the graph, rules synced from git, and an MR bot that posts each change's blast radius.
Google Cloud
StableBigQuery, Dataform, Data Fusion, Cloud Storage, Pub/Sub, Composer, Cloud Run and more: 25 asset types.
MicroStrategy
StableCubes, dossiers, reports and schedules, with lineage from dossier to cube to warehouse, including SAP HANA tables.