feat: enable levels to cache sstables to local disk if uploaded to S3 #356
Conversation
This file contains hidden or 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
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
crwen
reviewed
Jun 17, 2025
tmp modify tmp commit feat: enable levels to cache sstables to local disk if uploaded to S3 feat: enable levels to cache sstables to local disk if uploaded to S3 fix ci & unit test & format fix ut fix wasm & python ci fix ci remove garbage info & fix token
|
Is it better to fix format CI and binding CI first |
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.
If level in lsm tree is set as remote storage(S3), then sstables in this level can be stored in local disk as cache by setting cached as true.