What problem does it solve?
Data quality failures quietly propagate through pipelines, corrupting dashboards, training models on flawed data, and breaking downstream consumers without clear ownership or early signals.
Core Features & Use Cases
- Validate schemas and expectations at boundaries: Add ingress/serving quality gates using schema validation and Great Expectations suites so issues like null spikes, missing columns, and constraint violations are caught early.
- Create data contracts between producers and consumers: Define versioned YAML contracts covering schema, semantics, SLAs, and ownership to prevent breaking changes and clarify escalation paths.
- Implement monitoring and lineage for impact analysis: Set up freshness/volume anomaly checks and track lineage (including impact of schema changes) using OpenLineage-compatible patterns.
Quick Start
Run data-quality guidance to define an orders Great Expectations suite, a data contract, and the monitoring checks for freshness, volume anomalies, and schema drift.