Merge pull request #3359 from liyun95/v2.6.x

update json shredding configs & 2.6.5 release notes

Author: liyun95

site/en/Variables.json

@@ -1,18 +1,18 @@
 {
-  "milvus_release_version": "2.6.4",
-  "milvus_release_tag": "2.6.4",
+  "milvus_release_version": "2.6.5",
+  "milvus_release_tag": "2.6.5",
   "milvus_deb_amd64": "milvus_2.6.0-1_amd64.deb",
   "milvus_rpm_amd64": "milvus_2.6.0-1_amd64.rpm",
   "milvus_deb_arm64": "milvus_2.6.0-1_arm64.deb",
   "milvus_rpm_arm64": "milvus_2.6.0-1_arm64.rpm",
   "milvus_python_sdk_version": "2.4.x",
   "milvus_python_sdk_real_version": "2.6.3",
   "milvus_node_sdk_version": "2.4.x",
-  "milvus_node_sdk_real_version": "2.6.1",
+  "milvus_node_sdk_real_version": "2.6.4",
   "milvus_go_sdk_version": "2.3.x",
   "milvus_go_sdk_real_version": "2.6.1",
   "milvus_java_sdk_version": "2.4.x",
-  "milvus_java_sdk_real_version": "2.6.6",
+  "milvus_java_sdk_real_version": "2.6.7",
   "milvus_csharp_sdk_version": "2.2.x",
   "milvus_csharp_sdk_real_version": "2.2.14", 
   "milvus_restful_sdk_version": "2.4.x",

site/en/release_notes.md

@@ -8,6 +8,33 @@ title: Release Notes
 
 Find out what’s new in Milvus! This page summarizes new features, improvements, known issues, and bug fixes in each release. You can find the release notes for each released version after v2.6.0 in this section. We suggest that you regularly visit this page to learn about updates.
 
+## v2.6.5
+
+Release date: November 11, 2025
+
+| Milvus Version | Python SDK Version | Node.js SDK Version | Java SDK Version | Go SDK Version |
+|:-------------- |:------------------|:--------------------|:-----------------|:---------------|
+| 2.6.5          | 2.6.3             | 2.6.4               | 2.6.7            | 2.6.1          |
+
+We are excited to announce the release of Milvus 2.6.5, which addresses a **critical security vulnerability** [CVE-2025-64513](https://github.com/milvus-io/milvus/security/advisories/GHSA-mhjq-8c7m-3f7p) and upgraded to Go 1.24.9. We strongly encourage **all Milvus 2.6.x users to upgrade to 2.6.5** as soon as possible. This update also includes several other improvements and bug fixes, and provides the users a more robust and efficient experience.
+
+### Improvements
+
+- Updated builder image tag upgrading go1.24.9 ([#45398](https://github.com/milvus-io/milvus/pull/45398))
+- Skipped check source id ([#45379](https://github.com/milvus-io/milvus/pull/45379))
+
+### Bug fixes
+
+- Group value is nil ([#45421](https://github.com/milvus-io/milvus/pull/45421))
+- Initialized timestamp range in composite binlog writer  ([#45402](https://github.com/milvus-io/milvus/pull/45402))
+- Handled empty fieldsdata in reduce/rerank for requery scenario  ([#45389](https://github.com/milvus-io/milvus/pull/45389))
+- Added null check for packed_writer_ in jsonstatsparquetwrite… ([#45376](https://github.com/milvus-io/milvus/pull/45376))
+- Skipped building text index for newly added columns ([#45358](https://github.com/milvus-io/milvus/pull/45358))
+- Accidentally ignored sealed segments in l0 compaction ([#45351](https://github.com/milvus-io/milvus/pull/45351))
+- Moved finishload before text index creation to ensure raw data availability ([#45336](https://github.com/milvus-io/milvus/pull/45336))
+- Supported json default value in compaction ([#45332](https://github.com/milvus-io/milvus/pull/45332))
+- Updated milvus-storage to fix duplicate aws sdk initialization  ([#45075](https://github.com/milvus-io/milvus/pull/45075))
+
 ## v2.6.4
 
 Release date: October 21, 2025

site/en/userGuide/schema/json-shredding.md

@@ -88,13 +88,13 @@ The final phase leverages the optimized storage layout to intelligently select t
 
 ## Enable JSON shredding
 
-To activate the feature, set `common.enabledJSONKeyStats` to `true` in your `milvus.yaml` configuration file. New data will automatically trigger the shredding process.
+To activate the feature, set `common.enabledJSONShredding` to `true` in your `milvus.yaml` configuration file. New data will automatically trigger the shredding process.
 
 ```yaml
 # milvus.yaml
 ...
 common:
-  enabledJSONKeyStats: true # Indicates whether to enable JSON key stats build and load processes
+  enabledJSONShredding: true # Indicates whether to enable JSON key stats build and load processes
 ...
 ```
 
@@ -112,34 +112,34 @@ For most users, once JSON shredding is enabled, the default settings for other p
      <th><p>Tuning Advice</p></th>
    </tr>
    <tr>
-     <td><p><code>common.enabledJSONKeyStats</code></p></td>
+     <td><p><code>common.enabledJSONShredding</code></p></td>
      <td><p>Controls whether the JSON shredding build and load processes are enabled.</p></td>
      <td><p>false</p></td>
      <td><p>Must be set to <strong>true</strong> to activate the feature.</p></td>
    </tr>
    <tr>
-     <td><p><code>common.usingJsonStatsForQuery</code></p></td>
+     <td><p><code>common.usingjsonShreddingForQuery</code></p></td>
      <td><p>Controls whether Milvus uses shredded data for acceleration.</p></td>
      <td><p>true</p></td>
      <td><p>Set to <strong>false</strong> as a recovery measure if queries fail, reverting to the original query path.</p></td>
    </tr>
    <tr>
-     <td><p><code>queryNode.mmap.jsonStats</code></p></td>
-     <td><p>Determines whether Milvus uses mmap when loading shredding data.</p><p>For details, refer to <a href="mmap.md">Use mmap</a>.</p></td>
+     <td><p><code>queryNode.mmap.jsonShredding</code></p></td>
+     <td><p>Determines whether Milvus uses mmap when loading shredding data.</p><p>For details, refer to <a href="https://zilliverse.feishu.cn/wiki/P3wrwSMNNihy8Vkf9p6cTsWYnTb">Use mmap</a>.</p></td>
      <td><p>true</p></td>
      <td><p>This setting is generally optimized for performance. Only adjust it if you have specific memory management needs or constraints on your system.</p></td>
    </tr>
    <tr>
-     <td><p><code>dataCoord.jsonStatsMaxShreddingColumns</code></p></td>
+     <td><p><code>dataCoord.jsonShreddingMaxColumns</code></p></td>
      <td><p>The maximum number of JSON keys that will be stored in shredded columns. </p><p>If the number of frequently appearing keys exceeds this limit, Milvus will prioritize the most frequent ones for shredding, and the remaining keys will be stored in the shared column.</p></td>
      <td><p>1024</p></td>
      <td><p>This is sufficient for most scenarios. For JSON with thousands of frequently appearing keys, you may need to increase this, but monitor storage usage.</p></td>
    </tr>
    <tr>
-     <td><p><code>dataCoord.jsonStatsShreddingRatioThreshold</code></p></td>
+     <td><p><code>dataCoord.jsonShreddingRatioThreshold</code></p></td>
      <td><p>The minimum occurrence ratio a JSON key must have to be considered for shredding into a shredded column.</p><p>A key is considered frequently appearing if its ratio is above this threshold.</p></td>
      <td><p>0.3</p></td>
-     <td><p><strong>Increase</strong> (e.g., to 0.5) if the number of keys that meet the shredding criteria exceeds the <code>dataCoord.jsonStatsMaxShreddingColumns</code> limit. This makes the threshold stricter, reducing the number of keys that qualify for shredding.</p><p><strong>Decrease</strong> (e.g., to 0.1) if you want to shred more keys that appear less frequently than the default 30% threshold.</p></td>
+     <td><p><strong>Increase</strong> (e.g., to 0.5) if the number of keys that meet the shredding criteria exceeds the <code>dataCoord.jsonShreddingMaxColumns</code> limit. This makes the threshold stricter, reducing the number of keys that qualify for shredding.</p><p><strong>Decrease</strong> (e.g., to 0.1) if you want to shred more keys that appear less frequently than the default 30% threshold.</p></td>
    </tr>
 </table>
 
@@ -231,13 +231,15 @@ This test focused on querying sparse, nested keys that fall into the "shared" ca
 
     1. Next, verify that the data has been loaded by running `show loaded-json-stats` on the query node. The output will display details about the loaded shredded data for each query node.
 
+- **What if I encounter an error?**
+
+    If the build or load process fails, you can quickly disable the feature by setting `common.enabledJSONShredding=false`. To clear any remaining tasks, use the `remove stats-task <task_id>` command in [Birdwatcher](birdwatcher_usage_guides.md). If a query fails, set `common.usingjsonShreddingForQuery=false` to revert to the original query path, bypassing the shredded data.
+
 - **How do I select between JSON shredding and JSON indexing?**
 
     - **JSON shredding** is ideal for keys that appear frequently in your documents, especially for complex JSON structures. It combines the benefits of columnar storage and inverted indexing, making it well-suited for read-heavy scenarios where you query many different keys. However, it is not recommended for very small JSON documents as the performance gain is minimal. The smaller the proportion of the key's value to the total size of the JSON document, the better the performance optimization from shredding.
 
     - **JSON indexing** is better for targeted optimization of specific key-based queries and has lower storage overhead. It's suitable for simpler JSON structures. Note that JSON shredding does not cover queries on keys inside arrays, so you need a JSON index to accelerate those.
 
-- **What if I encounter an error?**
-
-    If the build or load process fails, you can quickly disable the feature by setting `common.enabledJSONKeyStats=false`. To clear any remaining tasks, use the `remove stats-task <task_id>` command in [Birdwatcher](birdwatcher_usage_guides.md). If a query fails, set `common.usingJsonStatsForQuery=false` to revert to the original query path, bypassing the shredded data.
+    For details, refer to [JSON Field Overview](json-field-overview.md#Next-Accelerate-JSON-queries).