-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ENH]: add batch get version file paths method to Sysdb #4432
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
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
ab87d31
to
7e6889e
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. |
7e6889e
to
ea31ef5
Compare
ea31ef5
to
4d29f0d
Compare
4d29f0d
to
0d136b9
Compare
Add Batch Get Version File Paths Method to Sysdb API (Rust/Go) This PR introduces a new batch_get_collection_version_file_paths method to the Sysdb system in both Rust and Go, enabling clients to retrieve version file paths for multiple collection IDs in one request. The change modifies API layers end-to-end: protocol buffer definition, Go DB/data access, service and coordinator logic, and their test coverage. It mainly supports garbage collection and related collection tree operations by streamlining access to version files. Key Changes: Affected Areas: This summary was automatically generated by @propel-code-bot |
93be17d
to
ea366a5
Compare
b39fd56
to
8a3421d
Compare
ea366a5
to
edf6743
Compare
8a3421d
to
972427e
Compare
505c4ae
to
3ece42b
Compare
972427e
to
bab5b68
Compare
3ece42b
to
5801be6
Compare
5801be6
to
90ac80a
Compare
bab5b68
to
5f7fa4a
Compare
90ac80a
to
2e26e8a
Compare
5f7fa4a
to
71c953d
Compare
2e26e8a
to
7344e5c
Compare
7344e5c
to
c3a7502
Compare
c3a7502
to
2425e04
Compare
Description of changes
Needed when garbage collecting a collection in a fork tree, because we need to read the version files of all other nodes in the tree.
Test plan
How are these changes tested?
Added a test.
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?
n/a