Add filter-based deletion to VectorStore implementations, Chroma, Elastic, PGVector #2106
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
Add string-based filter deletion alongside the Filter.Expression-based deletion for vector stores. This provides a more convenient API for simple filter cases while maintaining the full flexibility of expression-based filtering. Key changes: - Add delete(Filter.Expression) and delete(String) methods to VectorStore - Add default string filter implementation in VectorStore interface - Implement filter deletion in Chroma/Elasticsearch/PgVector stores - Add integration tests for both filter APIs across implementations This extends vector store deletion capabilities while maintaining consistent behavior across implementations.
markpollack
changed the title
|
merged in f588716 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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 the ability to delete documents from vector stores using filter expressions. This allows for more flexible document deletion based on metadata criteria rather than just document IDs.
Key changes:
This extends the VectorStore API to support more sophisticated document management capabilities while maintaining consistent behavior across different backend implementations.