Backfill Only the History Your Logic Change Actually Alters
Choose a defensible backfill strategy after a dbt logic change.
The situation A business definition changed, but only for a subset of historical records. Rebuilding everything would feel safe, yet it may hide whether anyone actually understood the scope. The costliest mistake is confusing “shared metric” with “all history must move.” Use the framework, not the reflex Backfill from the changed rule outward Start with the new business rule, translate it into affected rows, then rebuild only the nodes whose published answers depend on those rows. Common shortcut Fast locally, expensive downstream. You trade a little short-term effort for less hidden rework. Correctness comes from scoping the semantic impact precisely…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in