LogDb: Range Scan RFC - #476
Draft
hachikuji wants to merge 6 commits into
Draft
Conversation
hachikuji
force-pushed
the
worktree-logdb-global-scan
branch
from
August 6, 2026 16:57
7b5bc89 to
b3d877d
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This RFC proposes an approach for efficient range scans. A range scan involves scanning the logs for a range of keys at one time rather than reading each log individually. This would include global scans of all logs. We achieve this by tracking progress as l0s/wals are added to the manifest. The position is tracked with a manifest coordinate which defines a checkpoint tied to a specific manifest version and the location within the manifest (sst, last_key).