-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[ENH] Implement GetCollectionWithSegments endpoint for SysDB #3243
[ENH] Implement GetCollectionWithSegments endpoint for SysDB #3243
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
8de0623
to
f164019
Compare
|
||
res.Collection = convertCollectionToProto(collection) | ||
segmentpbList := make([]*coordinatorpb.Segment, 0, len(segments)) | ||
for _, segment := range segments { |
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.
nit: would it make sense to add validation here that a collection will have exactly 3 segments and that too the record, metadata and vector?
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.
I've added some checks for this
f164019
to
d13f790
Compare
11e3b2e
to
7be4e08
Compare
7be4e08
to
8d89a3e
Compare
Description of changes
Summarize the changes made by this PR.
GetCollectionWithSegments
interface for SysDB, which should return information about a consistent snapshot for a collection and its segmentsTest plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?