feat(langchain-community/pgvector): add support for advanced metadata filters in similarity search #8842
Conversation
This file contains hidden or 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
🦋 Changeset detectedLatest commit: 0882997 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
hntrl
reviewed
Sep 5, 2025
Member
hntrl
left a comment
hntrl
left a comment
There was a problem hiding this comment.
Looks good! couple of Q's:
- Could we add to the pgvector docs for these filter types?
- Could we rework the
Metadatatype on line 11 to understand these new filter types?
Contributor
Author
|
Thank you @hntrl for the review. |
- Introduced a new `MetadataFilter` type to define the structure of filter objects. - Implemented a `buildFilterClauses` method to dynamically construct SQL WHERE clauses based on the provided filters. - Updated PGVectorStore documentation Fix: - deleteByFilter method didn't apply complex filters at all, now it uses 'buildFilterClauses' to build the proper query string; New tests: - Expanded integration tests to cover all new filtering functionalities, ensuring correct behavior for each operator. - Refactored existing tests to utilize the new filtering structure, improving test clarity and coverage.
Contributor
Author
|
artemkdr
changed the title
… StrictMetadataFilter as a new one
urakozz
reviewed
Sep 8, 2025
| * { | ||
| * category: "test", // Simple equality | ||
| * score: { gte: 80 }, // Operator filter | ||
| * tags: { in: ["test1", "test2"] } // Another operator filter |
hntrl
approved these changes
Sep 9, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for advanced metadata filters in PGVector similarity search
This PR enhances the PGVector vector store integration by adding support for advanced metadata filtering capabilities during similarity search operations.
Changes
Benefits
Testing
This enhancement makes the PGVector integration more powerful and flexible for applications that need to combine semantic similarity with metadata-based filtering.