-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[ENH] Proto defs for collection version file. #950 #3453
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
Conversation
Please tag your PR title with one of: [ENH | BUG | DOC | TST | BLD | PERF | TYP | CLN | CHORE]. See https://docs.trychroma.com/contributing#contributing-code-and-ideas |
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
idl/chromadb/proto/coordinator.proto
Outdated
// NOTE: As of now, we only support version change due to data compaction. | ||
// There is a good chance to include other reasons in the future, especially | ||
// for DDL operations, recovery, etc. | ||
enum VersionChangeReason { |
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.
If this feels like over-engineering at this point, then i will just remove this. And add it later if/when we decide to increase versions for non-compaction purposes.
Includes proto for storing VersionHistory file, and new GRPCs in SysDb. There will be few more to support the GC tool/server that will follow later.
8b39781
to
1c5c497
Compare
Description of changes
Proto definitions and GRPC defs for supporting Versioned Collections.
Part of GC work.
Summarize the changes made by this PR.
Test 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?
n/a