Skip to main content
The milvus backend embeds knowledge chunks and stores them in a Milvus collection. Use it when you already operate Milvus or need local persistence through Milvus Lite. The VeADK index maps to the Milvus collection name.

Prerequisites

Install the VeADK extensions and configure an embedding model:
A remote deployment also requires a Milvus URI and credentials. For local validation, point DATABASE_MILVUS_URI to a Milvus Lite database file.

Use Milvus Lite

The first run creates data in ./data/company_faq.db. Later processes using the same file and collection name can retrieve the stored content.

Connect to remote Milvus

You can also pass the public configuration object:
Inject credentials through environment variables or a secret manager. Do not commit real tokens to source control.

Parameters

Constructor parameters

Milvus configuration

Setting DATABASE_MILVUS_OVERWRITE=true replaces the collection and its data. Use it only when the data can be rebuilt.

Embedding configuration

Last modified on September 19, 2026