llama-stack/llama_stack/providers/remote/vector_io
Ashwin Bharambe 330cc9d09d
feat: add Milvus vectorDB (#1467)
# What does this PR do?
See https://github.com/meta-llama/llama-stack/pull/1171 which is the
original PR. Author: @zc277584121

feat: add [Milvus](https://milvus.io/) vectorDB

note: I use the MilvusClient to implement it instead of
AsyncMilvusClient, because when I tested AsyncMilvusClient, it would
raise issues about evenloop, which I think AsyncMilvusClient SDK is not
robust enough to be compatible with llama_stack framework.

## Test Plan
have passed the unit test and ene2end test
Here is my end2end test logs, including the client code, client log,
server logs from inline and remote settings

[test_end2end_logs.zip](https://github.com/user-attachments/files/18964391/test_end2end_logs.zip)

---------

Signed-off-by: ChengZi <chen.zhang@zilliz.com>
Co-authored-by: Cheney Zhang <chen.zhang@zilliz.com>
2025-03-06 20:59:31 -08:00
..
chroma feat: allow conditionally enabling providers in run.yaml (#1321) 2025-03-01 11:19:14 -08:00
milvus feat: add Milvus vectorDB (#1467) 2025-03-06 20:59:31 -08:00
pgvector fix(pgvector): replace hyphens with underscores in table names (#1385) 2025-03-04 07:06:35 -08:00
qdrant chore: move all Llama Stack types from llama-models to llama-stack (#1098) 2025-02-14 09:10:59 -08:00
sample chore: Consistent naming for VectorIO providers (#1023) 2025-02-13 13:15:49 -05:00
weaviate chore: Consistent naming for VectorIO providers (#1023) 2025-02-13 13:15:49 -05:00
__init__.py [memory refactor][1/n] Rename Memory -> VectorIO, MemoryBanks -> VectorDBs (#828) 2025-01-22 09:59:30 -08:00