Milvus v2.6.17

v2.6.17

milvus-2.6.17

Added 1
  • Add ARRAY_APPEND and ARRAY_REMOVE partial update operators for Array fields, exposed through both gRPC and REST upsert APIs
Changed 1
  • Improve load/search isolation by using separate C++ executor pools and converting SegmentLoad and ReopenSegment to async futures with proper context cancellation
Fixed 6
  • Fix an issue where filter expression templates could not be used with string field predicates
  • Fix an issue where stale segment distribution updates after delegator close could corrupt query routing
  • Fix an issue where releasing a collection could leave stale replica state due to premature metadata cleanup in QueryCoord
  • Fix an issue where transient shard errors caused replicas to be blacklisted, leading to unnecessary query failures and degraded availability
  • Fix missing GetReplicateConfiguration RPC forwarding in the proxy service
  • Fix a potential use-after-free crash when closing the packed writer multiple times or during compaction cleanup paths
v2.6.17

Release date: May 22, 2026

Milvus VersionPython SDK VersionNode.js SDK VersionJava SDK VersionGo SDK Version
2.6.172.6.142.6.142.6.202.6.4

We are excited to announce the release of Milvus v2.6.17! This release introduces Array field partial update operators, improves load/search isolation, and resolves several stability and query routing issues.

Improvements
Bug fixes
  • Fixed an issue where filter expression templates could not be used with string field predicates (#49703)
  • Fixed an issue where stale segment distribution updates after delegator close could corrupt query routing (#49727)
  • Fixed an issue where releasing a collection could leave stale replica state due to premature metadata cleanup in QueryCoord (#49730)
  • Fixed an issue where transient shard errors caused replicas to be blacklisted, leading to unnecessary query failures and degraded availability (#49740, #49776)
  • Fixed missing GetReplicateConfiguration RPC forwarding in the proxy service (#49810)
  • Fixed a potential use-after-free crash when closing the packed writer multiple times or during compaction cleanup paths (#49816)
View original

Upgraded? How did it go?

Discussion