-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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] Add rust client to log service #1811
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
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.
lgtm, let's add e2e tests later
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.
- Let's return Result<> where appropriate and define our Error types. You can take a look at sysdb.rs for this
- I find the naming incongruence between the service definition and the client a bit odd. Can you explain the reasoning here? Also things like get_collections() and index feel like confusing names, can we improve those? Aligning with the service definition is an easy win, but open to other ideas. The service definition has verbose, but clear names.
- You can make your impl of Try_From on the Box<>'ed type instead. Box::new() will perform an allocation so we'd prefer one-copy reads of the record.
These should be pretty quick changes !! Thanks. Looks great otherwise.
let proto_submit = record_log.record.unwrap(); | ||
let proto_submit = record_log | ||
.record | ||
.ok_or(EmbeddingRecordConversionError::DecodeError( |
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.
nice use of ok_or!
## Description of changes *Summarize the changes made by this PR.* - Improvements & Bug fixes - ... - New functionality - This PR adds functionality to read logs from log service and get collections to compact. ## Test plan *How are these changes tested?* - [ ] Unit tests ## Documentation Changes *Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs repository](https://github.com/chroma-core/docs)?*
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?