refactor!: Refactor AlloyDBVectorStore to depend on PGVectorstore #435
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
product-auto-label
bot
added
the
api: alloydb
averikitsch
reviewed
Jul 30, 2025
dishaprakash
force-pushed
the
refactor-vs
branch
from
371ecdd to
b71ff05
Compare
averikitsch
approved these changes
Aug 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
refactor!: Refactor AlloyDBVectorStore to depend on PGVectorstore
AlloyDBAsyncVectorStore and AlloyDBVectorStore are refactored to depend on the AsyncPGVectorStore and PGVectorStore respectively.
Hybrid search is now supported in AlloyDBVectorStore. Tests for hybrid search have been added.
BREAKING CHANGE:
The support for text filters in similiarity searches has been removed, and we support only dictionary filters now.
The dependency on langchain-core and pgvector is based on LangChain-Postgres's specifications.