Convert Milvus provider configuration to be derivative

Created on 15 April 2025, 9 days ago

Problem/Motivation

This module currently provides a single AiVdbProvider plugin instance with information stored in ai_vdb_provider_milvus.settings. It would be useful to have multiple configured Milvus/Zilliz connections and derive an AiVdbProvider for each configured connection.

An example would be wanting to use Zillis/Milvus and have collections per-index. Currently you can only have one configured Milvus provider that references a specific collection for all indexes that must use Milvus. This is too restrictive.

Steps to reproduce

Proposed resolution

Convert to a configuration entity and allow multiple collection configurations. Derive AiVdbProvider plugins for each Milvus config entity.

Remaining tasks

- Decide if proposed resolution is appropriate.
- Add backing config entity.
- Add plugin deriver.

User interface changes

- Simple admin backend for managing the Milvus config entities.

API changes

Configuration settings object is converted to a configuration entity, and the VdbAiProvider plugin becomes a deriver. Permission modifications might be needed.

Data model changes

None.

✨ Feature request
Status

Active

Version

1.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States lpeabody

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024