Skip to main content
net10.0

Milvus vector provider for Koan: entity-first KNN search, metadata-filter pushdown, bulk operations, and collection management over REST.

Published
Jul 23, 2026
3mo ago
Total Downloads
3.9K
3,866

Install

dotnet add package Sylin.Koan.Data.Vector.Connector.Milvus --version 0.20.3
ProductVersions
.NET
net10.0

README

Sylin.Koan.Data.Vector.Connector.Milvus

Use Milvus behind Koan's entity-first vector API. Referencing this package activates the adapter; AddKoan() handles registration, provider election, naming, health participation, and startup reporting.

The generated product surface owns support maturity; this page owns Milvus setup and limits.

Install and use

dotnet add package Sylin.Koan.Data.Vector.Connector.Milvus
public sealed class Article : Entity<Article> { }

await Vector<Article>.Save(article.Id, embedding, new { category = "support" });
var matches = await Vector<Article>.Search(embedding, topK: 12);

No Milvus-specific registration is required. The zero-configuration endpoint is http://localhost:19530. Configure another deployment with Koan:Data:Milvus:Endpoint; use Token or Username/Password when authentication is enabled.

The first write establishes vector dimension. Set Koan:Data:Milvus:Dimension only when an empty collection must be created before the first write. Koan defaults topK to 10; an explicit positive value is sent unchanged.

Honest capability boundary

Milvus supports KNN search, native metadata-filter pushdown, bulk writes/deletes, collection clear, dynamic collection naming, and normalized cosine scores. The current adapter does not provide embedding reads, export, hybrid text search, search continuation tokens, or index statistics. Delete visibility follows the configured Milvus consistency posture and is not claimed as immediately observable.

Avoid pinning CollectionName in partitioned or tenant-isolated applications unless one shared collection is truly intended. A fixed name bypasses Koan's physical-name folds, and the runtime reports that correction.

See TECHNICAL.md for configuration, deployment shape, health, and failure behavior.

Changes from Previous Version

No structural changes between v0.20.1 and v0.20.3.

Adoption Assessment

Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.