You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Drift detection silently ignores unexpected production features #4
detect_drift() derives the monitored feature list from the reference dataset and verifies only that those features are present in production.
If the production dataset gains one or more unexpected columns, they are silently ignored.
Why it matters
Unexpected columns can indicate an upstream schema/version change. Ignoring them makes schema drift invisible even though the monitoring system should surface contract changes.
Suggested fix
Compute both sides of the schema diff:
missing expected features
unexpected production features
Either fail fast on unexpected features or record them explicitly in the drift report under a schema-drift section.
Acceptance criteria
missing expected feature remains an explicit error
unexpected production feature is surfaced rather than ignored
target/known non-feature columns are handled deliberately
regression test covers an added production-only column
Verified that this is already fixed on main by a8884e5. detect_drift now rejects unexpected production columns, retains the explicit missing-feature error, and permits the optional churn target column. Existing regression tests cover the production-only column and optional target. The full suite passed today (236 tests including the new runtime-artifact tests in #6). Closing as already completed; this is not a new fix from today's work.
Activity
Ayushdevo commentedon Nov 9, 2026
Verified that this is already fixed on main by a8884e5. detect_drift now rejects unexpected production columns, retains the explicit missing-feature error, and permits the optional churn target column. Existing regression tests cover the production-only column and optional target. The full suite passed today (236 tests including the new runtime-artifact tests in #6). Closing as already completed; this is not a new fix from today's work.