Skip to content
BENIBIX Learn

Schema Drift

Also known as Schema Change, Upstream Schema Change

When the columns of new data change and no one says so.

Think of it like

Someone moves the chairs while you sleep. You walk in the dark and bump into one.

Example

The app team renames price to unit_price. The nightly load still runs, but the price column in the warehouse is now empty.

Why it matters

It is one of the most common causes of broken pipelines. The silent kind can go unnoticed for weeks.

Definition

Schema drift is when the shape of incoming data changes without warning. A column is added, renamed or dropped, or its type changes. The source team often makes the change for a good reason and does not know who reads the data. Downstream, a pipeline may crash. Worse, it may keep running and fill a column with blanks.
Schema is one of the signals in the bottom row. A monitor sees the columns change before the reports go wrong.

Common mistake

Letting a loader add and drop columns on its own, with no alert. The pipeline survives, but the reports quietly go wrong.

Key takeaways

  1. 1
    Unannounced change. Added, renamed, dropped or retyped.
  2. 2
    Loud or silent. A crash, or blanks that go unseen.
  3. 3
    Catch it early. Contracts and monitors spot it.

Compare