forked from chroma-core/chroma
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[CLN] Rename SubmitEmbeddingRecord to OperationRecord. Remove Topic c…
…oncept from Segment/Collection. (chroma-core#1933) ## Description of changes This PR has two high-level aims - Clean up artifacts of our design that were implicitly coupled to pulsar. Namely topics and multiplexing. - Begin a rename of SubmitEmbeddingRecord, EmbeddingRecord to names that more accurately reflect their intents. I apologize for how large this PR is, but in practice, breaking something up like this is not really feasible AFAICT, unless we allow test-breaking stacked PRs... *Summarize the changes made by this PR.* - Improvements & Bug fixes - Renames SubmitEmbeddingRecord to OperationRecord in order to more correctly identify what it is - a record of an Operation (future PRs will rename EmbeddingRecord as well to LogRecord to make its intent clearer). - An OperationRecord does not need to store collection_id. This was an artifact of the pulsar log when we needed to demux data. We now improve the Ingest interface by presenting producers/consumers over logical log streams by collection. - Remove the concept of topic from the Producer/Consumer interfaces - it is no longer needed in a post pulsar-world. This also means Collection/Segment don't need to store Topic. - Removed the AssignmentPolicy concept. This only existed for multiplexing - which is not a concept without pulsar. - Update the Rust code with the topic field removed and with the OperationRecord naming. - Update Go code with the SysDB changes (No assignment policy + no log) no as well as the OperationRecord naming. - New functionality - None ## Test plan *How are these changes tested?* - [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust ## 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)?*
- Loading branch information
Showing
86 changed files
with
1,196 additions
and
2,652 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.