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.
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(storage): introduce non-proto type for vnode bitmap #3030
feat(storage): introduce non-proto type for vnode bitmap #3030
Changes from all commits
4bb421e
8f8a53f
042d9bf
b25368c
93b06f3
0c0d742
86cc439
3eee2cb
728f899
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Looks a little strange. Are you sure every
VNodeBitmap
needs atable_id
? The most intuitive representation may be only bitmap inside (e.g.Vec<u8>
) of it, while thetable_id
is out of it (e.g.HashMap<u32, VNodeBitmap >
)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.
There will be a
VNodeBitmap
in everyKeyspace
of a state table, sotable_id
is in need here. Also,VNodeBitmap
will be added to the interface ofStateStore
, where we use it for read pruning. In this case,table_id
is also necessary. Any other case to useVNodeBitmap
?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.
And from the aspect of logic, the struct is designed for read pruning, which depends on state table. So having a
table_id
is reasonable, right? 🤔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.
Sounds reasonable 😁