-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[ENH] Add where collection filtering by metadata to distributed #5029
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
base: jai/local-collection-filtering
Are you sure you want to change the base?
[ENH] Add where collection filtering by metadata to distributed #5029
Conversation
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
4 Jobs Failed: PR checks / Python tests / test-rust-bindings (3.9, chromadb/test/property/test_cross_version_persist.py)
PR checks / Go tests / cluster-test
PR checks / Python tests / test-cluster-rust-frontend (3.9, chromadb/test/property/test_collections.py)
PR checks / Python tests / test-cluster-rust-frontend (3.9, chromadb/test/property/test_collections_with_database_tenant.py)No logs available for this step. Summary: 1 successful workflow, 1 failed workflow
Last updated: 2025-07-10 20:00:12 UTC |
568ad47
to
6898a15
Compare
Before we can implement this in distributed we need to consider if we have the right schema for performance. |
We also need to consider how this would affect future sharding plans, and what indexes we need to support this. Cc @sanketkedia. I think we are jumping to implementation hastily. |
sorry, did not mean to have opened this pr, was just messing around with implementation with claude code. closing |
I mean I think we should do this - just saying we need to consider how to do it |
1542c7f
to
281ce9a
Compare
6898a15
to
663500f
Compare
Description of changes
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 section?