Skip to content

Suggest article: testing a change-safety check on a 2M-row Delta table #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Brahmawritings wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Suggest article: testing a change-safety check on a 2M-row Delta table #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions weekly/safety-net-ai-agents-databricks.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
article:
author:
name: "Brahma"
twitter: "@BrahmaWritings"
link: "https://medium.com/towards-data-engineering/i-built-a-safety-net-for-ai-agents-on-databricks-then-i-tried-to-break-it-476983ea192c"
review: "Field notes from stress-testing a change-safety check on a 2-million-row Delta table on Databricks serverless. Covers Unity Catalog lineage that still reports dropped tables, null-safe key joins for data diffs, shallow clones as a sandbox for risky writes, and how a 10% sample hid a one-row delete until a full-table checksum was added. Disclosure: the author wrote the open-source tool the article tests."
tags: "data-quality, databricks, delta-lake, data-diff, lineage, ai-agents"