Schema Drift
Definition
Schema drift alters the agreed structure of incoming data.
An unexpected or uncoordinated change in the data structure compared to an agreed schema, such as fields, types, nesting, or mandatory status. Pure distribution changes are data drift; meaning changes are semantic drift.
Simply explained
A source suddenly delivers an expected numeric field as text or changes the structure of its data.
Why it matters in practice
The term improves reliable access to data and knowledge as well as their usable linkage in digital systems.
Example from business
A source suddenly delivers `price` as text instead of as a decimal number.
Limits and pitfalls
- Equating schema drift with data drift, checking only field names, not distinguishing compatible evolution and contract breach, or silently accepting changes.
Origin & history
Schema drift has become a common operational problem with data pipelines, data lakes, and event-driven systems.
Use in mid-sized companies
- Possible application: A source suddenly delivers `price` as text instead of as a decimal number.
Frequently asked questions
What does schema drift mean?
An unexpected or uncoordinated change in the data structure compared to an agreed schema, such as fields, types, nesting, or mandatory status. Pure distribution changes are data drift; meaning changes are semantic drift. What mistakes should be avoided? Equating schema drift with data drift, checking only field names, not distinguishing compatible evolution and contract breach, or silently accepting changes.
Sources
Source verified on 10.10.2026. Editorial application examples are hypothetical; no evidence of real customer results.
Editorially reviewed on: