Lesson 16
Concurrent Writes in Delta Lake: What Happens When Two Streaming Jobs Hit the Same Table?
Databricks Delta Lake uses optimistic concurrency control to manage concurrent writes from multiple streaming jobs. If two jobs try to modify conflicting data at the same time, one transaction succeeds while the other detects a conflict, fails validation, and automatically retries when possible. Non-conflicting appends usually succeed concurrently, but overlapping updates, merges, or deletes can trigger transaction conflicts and job retries.
Get the full lesson
Sign in to unlock everything beyond the preview — it's free.
- Take timestamped notes as you watch
- Read the full transcript and download resources
- Join the discussion and track your progress