-
Notifications
You must be signed in to change notification settings - Fork 209
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
feat: store manifest to oss #607
Conversation
b452577
to
4e6ec90
Compare
Codecov Report
@@ Coverage Diff @@
## main #607 +/- ##
==========================================
+ Coverage 66.07% 66.08% +0.01%
==========================================
Files 284 285 +1
Lines 43799 44299 +500
==========================================
+ Hits 28938 29275 +337
- Misses 14861 15024 +163
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
So many changes, could you point me which parts are most important to review? |
Actually, the massive changes result from the file path renaming: |
ba5d1e4
to
755c71e
Compare
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.
LGTM
* feat: store snapshot to object store * Store snapshot to oss * adapt to the new implementation * support convestion for snapshot and current snapshot * implement the SnapshotStore * update unit test * fix bug found by unit test * fix some comments * fix test_table_write_get_override_mem_wal caused by resetting seq of mem wal * add TODO for delete logs after snapshotting * refactor the manifest api: load_data * remove debug println * fix failure of ut * rename mod manifest to meta * address CR * avoid indirect current snapshot file * handle snapshot not exist
Which issue does this PR close?
Closes #579
Rationale for this change
Details have been provided in the #579. The basic targes include:
What changes are included in this PR?
Implement the proposal: #579 (comment)
Are there any user-facing changes?
None.
How does this change test
Existing tests.