-
Notifications
You must be signed in to change notification settings - Fork 62
[otap-df-quiver] Add Write-Ahead-Log (WAL) implementation to Quiver #1537
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
base: main
Are you sure you want to change the base?
Conversation
… be based on logical cursor.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1537 +/- ##
==========================================
+ Coverage 83.48% 83.74% +0.26%
==========================================
Files 428 433 +5
Lines 118652 121877 +3225
==========================================
+ Hits 99054 102068 +3014
- Misses 19064 19275 +211
Partials 534 534
🚀 New features to boost your workflow:
|
| "MIT-0", | ||
| "Apache-2.0", | ||
| "Unicode-3.0", | ||
| "BSD-2-Clause", |
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.
Required due to the array-ref transitive dependency (from blake3) using this license. BSD-2-Clause is even more permissive than BSD-3-Clause (which is already allowed here), so I don't believe this should be a concern.
This pull request introduces an implementation of the Quiver write-ahead log (WAL). The most significant change from the initial spec includes a rewrite and clarification of the WAL file rotation and checkpointing mechanism. Documentation has been updated to reflect the new design.