v2.3.6
Release date: Jan 24, 2024
| Milvus version | Python SDK version | Java SDK version | Go SDK version | Node.js SDK version |
|---|---|---|---|---|
| 2.3.6 | 2.3.6 | 2.3.4 | 2.3.5 | 2.3.5 |
Milvus v2.3.6 marks a minor yet impactful update, concentrating on boosting overall functionality and stability. In this release, we've revamped QueryCoord to enhance stability, introduced support for array and JSON data types through RESTFul APIs, and amped up the speed of index loading. Alongside these enhancements, we've made several tweaks to optimize system performance and resource management. Additionally, this release addresses critical bug fixes as well as issues like memory leaks, load timeouts, and service unavailability, ensuring a more reliable and stable user experience.
Improvements
- Replace "leader_observer" with "leader_checker" to address concurrency issues related to loading and releasing segments (#29984 #30152).
- Transform specific magic numbers into configurable options (#30070).
- Remove heartbeat delay logic for ShardLeader to prevent misjudging its availability (#30085).
- When allocating channels, shuffle ShardLeader candidates to avoid load imbalance (#30089).
- Enhance RESTful support by adding functionality for arrays and JSON (#30077).
- Add a counter monitoring for rate-limited requests (#30132).
- Accelerate index loading through concurrent methods (#30018).
- Remove the step of DataNode subscribing to the message stream during the Import phase to avoid Import timeouts (#30133).
- Introduce association logic between privileges to simplify the authorization process (#30154).
- Implement unified restrictions on the number of Collections, Partitions, and Shards (#30017).
Critical bug fixes
- Fixed a memory leak caused by incorrect usage of OpenTelemetry in segcore (#30068).
- Addressed the issue of slow disk index loading by dynamically patching the index parameters (#30016).
- Resolved the problem of changes made through the "alter collection" command not being persisted (#30156).
- Fixed the issue where read request rate limiting ultimately leads to the unavailability of the read service (#30196).