-
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] add distributed implementation for database deletion #3460
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
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 |
This stack of pull requests is managed by Graphite. Learn more about stacking. |
8e3c1ca
to
9c8302f
Compare
66f9a9e
to
1c7f888
Compare
adc995d
to
1b4c82b
Compare
1c7f888
to
3e78b27
Compare
1b4c82b
to
edd88bf
Compare
aaa990a
to
9b9e736
Compare
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
edd88bf
to
b3dab70
Compare
9b9e736
to
2039415
Compare
Merge activity
|
2039415
to
ea0ac3a
Compare
Description of changes
Adds implementation for database deletion API to distributed Chroma.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustAdded a new Go test. Mostly tested with existing Python tests.
Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?
n/a