-
Notifications
You must be signed in to change notification settings - Fork 53
DOC: update overview page with more concrete examples #1391
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.
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
Conversation
|
|
||
| Transactions solve this by making all the writes atomic—they happen together or not at all. This is the foundation that makes Icechunk reliable enough to use as a database. | ||
|
|
||
| ### ACID Transactions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ACID transactions section is pretyt much claude vibing out explanations because I coudln't find a single great source to link to. But fairly confident it did a good job, but someone who understands this better than me should hopefully check
rabernat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is excellent. Sorry it took me so long to review.
Co-authored-by: Ryan Abernathey <[email protected]>
Co-authored-by: Ryan Abernathey <[email protected]>
I moved the old overview page into the new "concepts" page and re-wrote the overview to focus on three concrete improvements on top of zarr. I also tried to to structure it so that someone who knows what an ACID transaction is will still immediately be able to see what is going on, but for those who don't there is an easy path to learning what that is and why it is important.