Zum Hauptinhalt springen

Version the Promise, Not the File

Classify data contract changes as patch, minor, or major based on compatibility with consumer expectations.

data-contracts5 min read

Version numbers communicate compatibility. Patch Use patch when the contract's promise stays the same and you are correcting an implementation or documentation issue. Example: fixing a misspelled description or correcting a quality test that was weaker than the documented rule. Minor Use minor when you add capability without forcing consumers to change. Example: adding an optional nullable field, a new non-blocking quality warning, or additional metadata. Major Use major when a consumer's current expectation can break. Example: removing a field, changing an enum's meaning, changing table grain, changing a metric definition, or reducing freshness guarantees. If a downstream dashboard, model,…

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Kontakt aufnehmen