Skip to content

Add filter-based deletion to Qdrant vector store #2131

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

Conversation

sobychacko
Copy link
Contributor

Add string-based filter deletion alongside the Filter.Expression-based deletion for Qdrant vector store, providing consistent deletion capabilities with other vector store implementations.

Key changes:

  • Add delete(Filter.Expression) implementation using Qdrant's filter API
  • Leverage existing QdrantFilterExpressionConverter for filter translation
  • Use Qdrant's native deleteAsync with filter capabilities
  • Add comprehensive integration tests for filter deletion
  • Support both simple and complex filter expressions

This maintains consistency with other vector store implementations while utilizing Qdrant's native filtering capabilities for efficient metadata-based deletion.

Add string-based filter deletion alongside the Filter.Expression-based deletion
for Qdrant vector store, providing consistent deletion capabilities with
other vector store implementations.

Key changes:
- Add delete(Filter.Expression) implementation using Qdrant's filter API
- Leverage existing QdrantFilterExpressionConverter for filter translation
- Use Qdrant's native deleteAsync with filter capabilities
- Add comprehensive integration tests for filter deletion
- Support both simple and complex filter expressions

This maintains consistency with other vector store implementations while
utilizing Qdrant's native filtering capabilities for efficient metadata-based
deletion.

Signed-off-by: Soby Chacko <soby.chacko@broadcom.com>
@sobychacko sobychacko added this to the 1.0.0-M6 milestone Jan 28, 2025
@markpollack
Copy link
Member

merged in 81d5618

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants