●Change8

Migrating to Milvus v2.6.3

Version v2.6.3 introduces 1 breaking change. This guide details how to update your code.

Released: 10/31/2025

1
Breaking Changes
3
Migration Steps
10
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

MilvusClient.create_schemaMilvusClient.add_fieldMilvusClient.create_collectionMilvusClient.insertMilvusClient.queryMilvusClient.compactDataType.STRUCTDataType.ARRAYDataType.GEOMETRYAsyncMilvusClient

Breaking Changes

●Issue #1

String values are now treated as JSON-serialized bytes when inserting data. If you were inserting plain strings into fields expecting JSON serialization (or implicitly handled as such), you must now explicitly use `json.dumps()` on the string before insertion. Example fix: `client.insert(..., data=[{"id": 1, "json_field": json.dumps("a")}]`)

Migration Steps

  1. 1
    If inserting string data into fields that are now treated as JSON-serialized bytes, update insertion logic to use `json.dumps()` on the string value.
  2. 2
    If using auto_id collections, ensure `allow_insert_auto_id: "true"` is set in collection properties if you intend to manually provide primary keys during insertion.
  3. 3
    Review documentation links for Array of Structs and Geometry data types for usage details.

Release Summary

This release introduces major features including support for Array of Structs and Geometry data types, alongside manual L0 compaction control. A critical breaking change mandates JSON serialization for string data during insertion.

Need More Details?

View the full release notes and all changes for Milvus v2.6.3.

View Full Changelog