llama-stack/docs/source
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
..
building_applications docs: update test_agents to use new Agent SDK API (#1402) 2025-03-06 15:21:12 -08:00
concepts feat: add Milvus vectorDB (#1467) 2025-03-06 20:59:31 -08:00
contributing fix: update testing documentation 2025-03-05 17:41:13 -08:00
distributions docs: add information on how to set log level before running (#1430) 2025-03-06 10:54:14 -08:00
getting_started docs: update test_agents to use new Agent SDK API (#1402) 2025-03-06 15:21:12 -08:00
introduction Update index.md (#888) 2025-01-28 04:55:41 -08:00
playground fix!: update eval-tasks -> benchmarks (#1032) 2025-02-13 16:40:58 -08:00
providers feat: add Milvus vectorDB (#1467) 2025-03-06 20:59:31 -08:00
references docs: update eval doc (#1453) 2025-03-06 14:14:10 -08:00
conf.py fix: update version and fix docs release notes link 2025-03-03 11:48:57 -08:00
index.md feat: add Milvus vectorDB (#1467) 2025-03-06 20:59:31 -08:00