agentscope-ai / agentscope-ai/agentscope
feat(rag): support Redis vector search as a VDBStore backend
- Linguagem predominante
- Python
- Estrelas
- 31.6k
- Forks
- 3.5k
- Merge médio
- 1d 16h
- PRs com merge (30d)
- 103
Descrição
### Discussed in https://github.com/agentscope-ai/agentscope/discussions/2164
Originally posted by **izualzhy** July 23, 2026
## Feature Request
It would be great if AgentScope could support Redis Vector Search as a `VDBStore` backend.
Many users already have Redis deployed in production. Supporting Redis would allow them to build small and medium-sized RAG applications without introducing an additional vector database such as Qdrant or Milvus.
Redis Vector Search provides native support for vector indexing (HNSW/FLAT), similarity search, and metadata filtering, making it a good fit for the existing `KnowledgeBase` + `VDBStore` abstraction.
From my understanding of the current design, this could fit naturally into the existing architecture as another `VDBStore` implementation:
```
KnowledgeBase
│
▼
VectorStoreBase
│
┌────────────────┴────────────────┐
│ │ │
QdrantStore ... RedisVectorStore (new)
│
├── create collection / index
├── insert documents
├── vector search
├── delete documents
├── list documents
└── (metadata_filter)
```
This would provide a lightweight deployment option while keeping the current architecture unchanged.
If this feature aligns with the project roadmap, I'd be happy to contribute an implementation.
Guia de contribuição
Direção de pesquisa
Start at the existing VDBStore architecture referenced in the request: `KnowledgeBase` → `VectorStoreBase` and the current `QdrantStore` implementation. Find how backends are registered/selected there, then add a `RedisVectorStore` following the same contract for collection/index creation, insert, search, delete, list, and metadata filtering. Run the current tests that cover KnowledgeBase/vector-store behavior and any backend wiring docs; done means Redis is a selectable backend with passing related tests.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- python, redis
- Domínio
- databases
- Tipo de issue
- Funcionalidade
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 47/100