---
title: "Discussion on \"Schema Drift vs. Semantic Drift in Data Pipelines\" | Hashnode"
description: "Discussion on \"Schema Drift vs. Semantic Drift in Data Pipelines\". When a column is removed from a source database or dataset, the next pipeline run usually fails, making the problem easy to detect. But when a field keeps the same name and data type but its meaning c"
url: "https://hashnode.com/posts/schema-drift-vs-semantic-drift-in-data-pipelines/6af6f326f94aa3564f351d31"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Schema Drift vs. Semantic Drift in Data Pipelines](https://freecodecamp.org/news/schema-drift-vs-semantic-drift-in-data-pipelines?utm_source=hashnode&utm_medium=feed)

When a column is removed from a source database or dataset, the next pipeline run usually fails, making the problem easy to detect. But when a field keeps the same name and data type but its meaning c

5d ago · 23 min read · freecodecamp.org  
Read the article

-   [#data-pipelines](https://hashnode.com/tag/data-pipelines)
-   [#pydantic](https://hashnode.com/tag/pydantic)
-   [#python](https://hashnode.com/tag/python)
-   [#data-engineering](https://hashnode.com/tag/data-engineering)

## Written by

[Yemi Ojedapo](https://hashnode.com/@Hyemiie)

@Hyemiie

  
[View profile](https://hashnode.com/@Hyemiie)

Software developer, Technical writer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
