-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[CLN] Cleanup codebase with the refactored metadata filtering pipeline #2849
[CLN] Cleanup codebase with the refactored metadata filtering pipeline #2849
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @Sicheng-Pan and the rest of your teammates on Graphite |
Reviewer ChecklistPlease leverage this checklist to ensure your code review is thorough before approving Testing, Bugs, Errors, Logs, Documentation
System Compatibility
Quality
|
90b6d82
to
25b4e7a
Compare
034df37
to
61bd467
Compare
25b4e7a
to
19d282c
Compare
61bd467
to
20da0c5
Compare
19d282c
to
b0ea68d
Compare
20da0c5
to
936d0f6
Compare
b0ea68d
to
e5c7aec
Compare
936d0f6
to
4f86f02
Compare
e5c7aec
to
0f4d278
Compare
4f86f02
to
eecff23
Compare
} | ||
|
||
// DEPRECATED: This exists only for the legacy testing. Please checkout `MetadataFilteringOperator` for the up to date implementation. |
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.
curious, why did we not remove it? Is it just more work or are there other considerations?
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.
Simply because there's a lot unit tests depending on this and I'm not planning to refactor them altogether in this stack of PRs.
@@ -1164,10 +1164,11 @@ impl MetadataSegmentReader<'_> { | |||
}) | |||
} | |||
|
|||
// DEPRECATED: This exists only for the legacy testing. Please checkout `MetadataFilteringOperator` for the up to date implementation. | |||
pub async fn query( |
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.
curious, why did we not remove it? Is it just more work or are there other considerations?
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.
See above
0f4d278
to
5135e49
Compare
696d0ad
to
95af42d
Compare
Merge activity
|
*Summarize the changes made by this PR.* - Clean up warnings under rust/types. *How are these changes tested?* - `cargo clippy --all-targets` - [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust *Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs repository](https:/chroma-core/docs)?*
*Summarize the changes made by this PR.* - Improvements & Bug fixes - This switches to `debug_struct` over `f.write` as per @rescrv's suggestion. - Fixes a spurious warning about an unused struct field - New functionality - None *How are these changes tested?* We do not test the debug behavior. - [x] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust None
…2858) ## Description of changes *Summarize the changes made by this PR.* - Clean up warnings under rust/types. ## Test plan *How are these changes tested?* - `cargo clippy --all-targets` - [ ] 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:/chroma-core/docs)?*
*Summarize the changes made by this PR.* - clean up cache, distance, index, storage clippy warnings *How are these changes tested?* - cargo clippy locally - [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust *Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs repository](https:/chroma-core/docs)?*
Left some of worker untouched for concurrent PRs. *Summarize the changes made by this PR.* - Cleans up warnings. *How are these changes tested?* - [ ] cargo clippy && cargo test w/ tilt up. *Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs repository](https:/chroma-core/docs)?*
200ce7f
to
57505da
Compare
Description of changes
Summarize the changes made by this PR.
Test plan
How are these changes tested?
The existing tests should pass
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