docs: how delta lake transactions work #2089
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ion-elgreco
reviewed
Jan 19, 2024
|
|
||
| Delta Lake supports transactions which provide necessary reliability guarantees for production data systems. | ||
|
|
||
| Data lakes don’t provide transactions and this can cause nasty bugs and a bad user experience. Let’s look at a couple of scenarios when the lack of transactions cause a poor user experience: |
There was a problem hiding this comment.
Maybe call it vanilla data lakes? Delta lake in my opinion is just a data lake with a metadata layer
There was a problem hiding this comment.
Updated this. Delta Lakes def aren't data lakes 😱
See the Lakehouse paper. We usually call these "Lakehouse storage systems" or "open table formats".
djouallah
reviewed
Jan 19, 2024
|
|
||
| Durability means that all transactions that are successfully completed will always remain persisted, even if there are service outages or program crashes. | ||
|
|
||
| Suppose you have a Delta table that’s persisted in Azure blog storage. The Delta table transactions that are committed will always remain available, even in these circumstances: |
There was a problem hiding this comment.
good catch, lol. Thanks for reviewing!!
RobinLin666
pushed a commit
to RobinLin666/delta-rs
that referenced
this pull request
Feb 2, 2024
@nkarpov and I collaborated on this Delta Lake transactions post. It's meant to give the basics on how transactions work and why they're a huge advantage of Delta Lakes. @rtyler is giving a talk on transactions/concurrency soon. We're trying to set the stage with some foundational content first. --------- Co-authored-by: Ion Koutsouris <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@nkarpov and I collaborated on this Delta Lake transactions post.
It's meant to give the basics on how transactions work and why they're a huge advantage of Delta Lakes.
@rtyler is giving a talk on transactions/concurrency soon. We're trying to set the stage with some foundational content first.