milvus-io/milvus
v3.0.5Curated database / ai tools / vector-db / backend repository (milvus-io/milvus) tracked via conditional GitHub .atom polling.
@zilliz/milvus2-sdk-node is an open-source library and developer tool in the milvus-io/milvus ecosystem. It saves developers from writing repetitive low-level boilerplate from scratch by providing a battle-tested, open-source implementation ready for production.
Added per-resource-group load percentage and shard-leader. Review breaking API changes before upg… Migration: Moderate.
Key Release Highlights (v3.0.5)
- Added per-resource-group load percentage and shard-leader readiness in QueryCoord, and tagged each shard leader with its replica's resource group, so queries can be routed withi...
- Reduced copying in unscored Tantivy term queries by borrowing decoded postings blocks directly (#54469)
- Upgraded Knowhere to v3.0.17 and moved nullable vector offset mapping behind Knowhere APIs (#54473)
- Reduced memory allocations when encoding batched RESTful query and search responses by reusing per-request encoding buffers (#54540)
Breaking Changes (Action Required)
- Fixed an issue where QueryNode could panic while replaying encrypted WAL messages from a dropped database that shared a physical channel with other collections (#54640)
- Fixed an issue where index state was incorrectly reported as Failed when a partition was dropped while the index state was being queried (#54670)
npm install @zilliz/milvus2-sdk-node@3.0.5Ecosystem Compatibility Matrix & Verified Graph Warnings
Zero-Noise Historical Release Timeline (1)
Format: [Core Change] + [Required Action] + [Migration Effort]Added per-resource-group load percentage and shard-leader. Review breaking API changes before upg… Migration: Moderate.
Upgrade & Migration Q&A (milvus-io/milvus v3.0.5)
Direct Answers for Engineers & AI AgentsIs milvus-io/milvus v3.0.5 safe to upgrade in production?
milvus-io/milvus v3.0.5 is classified as BREAKING (PATCH release). Added per-resource-group load percentage and shard-leader. Review breaking API changes before upg… Migration: Moderate.
What breaking changes or compatibility risks exist in milvus-io/milvus v3.0.5?
Fixed an issue where QueryNode could panic while replaying encrypted WAL messages from a dropped database that shared a physical channel with other collections (#54640) Fixed an issue where index state was incorrectly reported as Failed when a partition was dropped while the index state was being queried (#54670)
What is the bundle size impact of @zilliz/milvus2-sdk-node v3.0.5?
Measured bundle size telemetry is currently unavailable for @zilliz/milvus2-sdk-node v3.0.5; verify build output locally before deploying.
How do I upgrade @zilliz/milvus2-sdk-node to v3.0.5?
Upgrade @zilliz/milvus2-sdk-node to v3.0.5 by running "npm install @zilliz/milvus2-sdk-node@3.0.5" and applying the migration steps: npm install @zilliz/milvus2-sdk-node@3.0.5