Release new docs to master

Author: Milvus-doc-bot

v2.5.x/Variables.json

@@ -1,16 +1,16 @@
 {
-  "milvus_release_version": "2.5.18",
-  "milvus_release_tag": "2.5.18",
+  "milvus_release_version": "2.5.19",
+  "milvus_release_tag": "2.5.19",
   "milvus_deb_name": "milvus_2.2.0-1_amd64",
   "milvus_rpm_name": "milvus-2.2.0-1.el7.x86_64",
   "milvus_python_sdk_version": "2.4.x",
   "milvus_python_sdk_real_version": "2.5.16",
   "milvus_node_sdk_version": "2.4.x",
-  "milvus_node_sdk_real_version": "2.5.12",
+  "milvus_node_sdk_real_version": "2.5.13",
   "milvus_go_sdk_version": "2.3.x",
   "milvus_go_sdk_real_version": "2.4.0",
   "milvus_java_sdk_version": "2.4.x",
-  "milvus_java_sdk_real_version": "2.5.13",
+  "milvus_java_sdk_real_version": "2.5.14",
   "milvus_csharp_sdk_version": "2.2.x",
   "milvus_csharp_sdk_real_version": "2.2.14", 
   "milvus_restful_sdk_version": "2.4.x",

v2.5.x/site/en/adminGuide/configure-docker.md

@@ -16,10 +16,10 @@ In current release, all parameters take effect only after Milvus restarts.
 
 ## Download a configuration file
 
-[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.5.18/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
+[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.5.19/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
 
 ```
-$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.18/configs/milvus.yaml
+$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.19/configs/milvus.yaml
 ```
 
 ## Modify the configuration file
@@ -178,13 +178,13 @@ Sorted by:
 
 ## Download an installation file
 
-Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.5.18/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`.
+Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.5.19/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`.
 
 You can also simply run the following command.
 
 ```
 # For Milvus standalone
-$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.18/milvus-standalone-docker-compose.yml -O docker-compose.yml
+$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.19/milvus-standalone-docker-compose.yml -O docker-compose.yml
 ```
 
 ## Modify the installation file

v2.5.x/site/en/adminGuide/operator.md

@@ -12,7 +12,7 @@ Milvus cluster depends on components including object storage, etcd, and Pulsar.
 
 This topic assumes that you have deployed Milvus Operator.
 
-<div class="alert note">See <a href="https://milvus.io/docs/v2.5.18/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
+<div class="alert note">See <a href="https://milvus.io/docs/v2.5.19/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
 
 You need to specify a configuration file for using Milvus Operator to start a Milvus cluster.
 

v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md

@@ -10,7 +10,7 @@ title: Upgrade Milvus Cluster with Docker Compose
 
 This topic describes how to upgrade your Milvus using Docker Compose. 
 
-In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.5.18.
+In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.5.19.
 
 ## Upgrade Milvus by changing its image
 
@@ -24,35 +24,35 @@ In normal cases, you can upgrade Milvus as follows:
     ...
     rootcoord:
       container_name: milvus-rootcoord
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ...
     proxy:
       container_name: milvus-proxy
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ...
     querycoord:
       container_name: milvus-querycoord
-      image: milvusdb/milvus:v2.5.18  
+      image: milvusdb/milvus:v2.5.19  
     ...
     querynode:
       container_name: milvus-querynode
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ...
     indexcoord:
       container_name: milvus-indexcoord
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ...
     indexnode:
       container_name: milvus-indexnode
-      image: milvusdb/milvus:v2.5.18 
+      image: milvusdb/milvus:v2.5.19 
     ...
     datacoord:
       container_name: milvus-datacoord
-      image: milvusdb/milvus:v2.5.18   
+      image: milvusdb/milvus:v2.5.19   
     ...
     datanode:
       container_name: milvus-datanode
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ```
 
 2. Run the following commands to perform the upgrade.
@@ -80,7 +80,7 @@ In normal cases, you can upgrade Milvus as follows:
       runWithBackup: true
     config:
       sourceVersion: 2.1.4   # Specify your milvus version
-      targetVersion: 2.5.18
+      targetVersion: 2.5.19
       backupFilePath: /tmp/migration.bak
     metastore:
       type: etcd

v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md

@@ -85,11 +85,11 @@ zilliztech/milvus       4.1.0           2.3.0                   Milvus is an ope
 
 You can choose the upgrade path for your Milvus as follows:
 
-<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.18.</div>
+<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.19.</div>
 
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.18.
+- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.19.
 
-- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.18.
+- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.19.
 
 <div style="display: none;">
 
@@ -111,10 +111,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
 | `w`          | New Milvus image tag                                      | `milvusdb/milvus:v2.2.3`         | True                    |
 | `o`          | Operation                                                 | `update`                         | False                   |
 
-Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.5.18.
+Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.5.19.
 
 ```shell
-sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.18 -w 'milvusdb/milvus:v2.5.18'
+sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.19 -w 'milvusdb/milvus:v2.5.19'
 ```
 
 <div class="alert note">

v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md

@@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu
 
 Once you have upgraded your Milvus operator to the latest version, you have the following choices:
 
-- To upgrade Milvus from v2.2.3 or later releases to 2.5.18, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
-- To upgrade Milvus from a minor release before v2.2.3 to 2.5.18, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
-- To upgrade Milvus from v2.1.x to 2.5.18, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
+- To upgrade Milvus from v2.2.3 or later releases to 2.5.19, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
+- To upgrade Milvus from a minor release before v2.2.3 to 2.5.19, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
+- To upgrade Milvus from v2.1.x to 2.5.19, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
 
 ## Conduct a rolling upgrade
 
@@ -47,7 +47,7 @@ spec:
   components:
     enableRollingUpdate: true
     imageUpdateMode: rollingUpgrade # Default value, can be omitted
-    image: milvusdb/milvus:v2.5.18
+    image: milvusdb/milvus:v2.5.19
 ```
 
 In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version.
@@ -63,7 +63,7 @@ spec:
   components:
     enableRollingUpdate: true
     imageUpdateMode: all
-    image: milvusdb/milvus:v2.5.18
+    image: milvusdb/milvus:v2.5.19
 ```
 
 You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
@@ -101,7 +101,7 @@ metadata:
 spec:
   # Omit other fields ...
   components:
-   image: milvusdb/milvus:v2.5.18
+   image: milvusdb/milvus:v2.5.19
 ```
 
 Then run the following to perform the upgrade:
@@ -112,11 +112,11 @@ kubectl patch -f milvusupgrade.yaml --patch-file milvusupgrade.yaml --type merge
 
 ## Migrate the metadata
 
-Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus 2.5.18.
+Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus 2.5.19.
 
 ### 1. Create a `.yaml` file for metadata migration
 
-Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.5.18`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.18.
+Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.5.19`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.19.
 
 ```
 apiVersion: milvus.io/v1beta1
@@ -128,9 +128,9 @@ spec:
     namespace: default
     name: my-release
   sourceVersion: "v2.1.4"
-  targetVersion: "v2.5.18"
+  targetVersion: "v2.5.19"
   # below are some omit default values:
-  # targetImage: "milvusdb/milvus:v2.5.18"
+  # targetImage: "milvusdb/milvus:v2.5.19"
   # toolImage: "milvusdb/meta-migration:v2.2.0"
   # operation: upgrade
   # rollbackIfFailed: true

v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md

@@ -14,7 +14,7 @@ title: Upgrade Milvus Standalone with Docker Compose
 
 This topic describes how to upgrade your Milvus using Docker Compose. 
 
-In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.5.18.
+In normal cases, you can [upgrade Milvus by changing its image](#Upgrade-Milvus-by-changing-its-image). However, you need to [migrate the metadata](#Migrate-the-metadata) before any upgrade from v2.1.x to v2.5.19.
 
 <div class="alter note">
 
@@ -32,7 +32,7 @@ In normal cases, you can upgrade Milvus as follows:
     ...
     standalone:
       container_name: milvus-standalone
-      image: milvusdb/milvus:v2.5.18
+      image: milvusdb/milvus:v2.5.19
     ```
 
 2. Run the following commands to perform the upgrade.
@@ -60,7 +60,7 @@ In normal cases, you can upgrade Milvus as follows:
       runWithBackup: true
     config:
       sourceVersion: 2.1.4   # Specify your milvus version
-      targetVersion: 2.5.18
+      targetVersion: 2.5.19
       backupFilePath: /tmp/migration.bak
     metastore:
       type: etcd

v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md

@@ -86,11 +86,11 @@ zilliztech/milvus       4.1.0           2.3.0                   Milvus is an ope
 
 You can choose the upgrade path for your Milvus as follows:
 
-<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.18.</div>
+<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.19.</div>
 
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.18.
+- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.19.
 
-- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.18.
+- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.19.
 
 <div style="display:none;">
 
@@ -112,10 +112,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
 | `w`          | New Milvus image tag                                      | `milvusdb/milvus:v2.2.3`         | True                    |
 | `o`          | Operation                                                 | `update`                         | False                   |
 
-Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.5.18.
+Once you have ensured that all deployments in your Milvus instance are in their normal status. You can run the following command to upgrade the Milvus instance to 2.5.19.
 
 ```shell
-sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.18 -w 'milvusdb/milvus:v2.5.18'
+sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.19 -w 'milvusdb/milvus:v2.5.19'
 ```
 
 <div class="alert note">
@@ -203,42 +203,42 @@ The following table lists the operations you can do for meta migration.
 4. Migrate the Milvus metadata.
 5. Start Milvus components with a new image.
 
-#### 2. Upgrade Milvus from v2.1.x to 2.5.18
+#### 2. Upgrade Milvus from v2.1.x to 2.5.19
 
-The following commands assume that you upgrade Milvus from v2.1.4 to 2.5.18. Change them to the versions that fit your needs.
+The following commands assume that you upgrade Milvus from v2.1.4 to 2.5.19. Change them to the versions that fit your needs.
 
 1. Specify Milvus instance name, source Milvus version, and target Milvus version.
 
     ```
-    ./migrate.sh -i my-release -s 2.1.4 -t 2.5.18
+    ./migrate.sh -i my-release -s 2.1.4 -t 2.5.19
     ```
 
 2. Specify the namespace with `-n` if your Milvus is not installed in the default K8s namespace.
 
     ```
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19
     ```
 
 3. Specify the root path with `-r` if your Milvus is installed with the custom `rootpath`.
 
     ```
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18 -r by-dev
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19 -r by-dev
     ```
 
 4. Specify the image tag with `-w` if your Milvus is installed with a custom `image`.
 
     ```
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18 -r by-dev -w milvusdb/milvus:v2.5.18
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19 -r by-dev -w milvusdb/milvus:v2.5.19
     ```
 
 5. Set `-d true` if you want to automatically remove the migration pod after the migration is completed.
 
     ```
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18 -w milvusdb/milvus:v2.5.18 -d true
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19 -w milvusdb/milvus:v2.5.19 -d true
     ```
 
 6. Rollback and migrate again if the migration fails.
 
     ```
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1
-    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.18 -r by-dev -o migrate -w milvusdb/milvus:v2.5.18
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1
+    ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.19 -r by-dev -o migrate -w milvusdb/milvus:v2.5.19

v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md

@@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu
 
 Once you have upgraded your Milvus operator to the latest version, you have the following choices:
 
-- To upgrade Milvus from v2.2.3 or later releases to 2.5.18, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
-- To upgrade Milvus from a minor release before v2.2.3 to 2.5.18, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
-- To upgrade Milvus from v2.1.x to 2.5.18, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
+- To upgrade Milvus from v2.2.3 or later releases to 2.5.19, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
+- To upgrade Milvus from a minor release before v2.2.3 to 2.5.19, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
+- To upgrade Milvus from v2.1.x to 2.5.19, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
 
 ## Conduct a rolling upgrade
 
@@ -47,7 +47,7 @@ spec:
   components:
     enableRollingUpdate: true
     imageUpdateMode: rollingUpgrade # Default value, can be omitted
-    image: milvusdb/milvus:v2.5.18
+    image: milvusdb/milvus:v2.5.19
 ```
 
 In this above configuration file, set `spec.components.enableRollingUpdate` to `true` and set `spec.components.image` to the desired Milvus version. 
@@ -63,7 +63,7 @@ spec:
   components:
     enableRollingUpdate: true
     imageUpdateMode: all
-    image: milvusdb/milvus:v2.5.18
+    image: milvusdb/milvus:v2.5.19
 ```
 
 You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
@@ -102,7 +102,7 @@ labels:
 spec:
   # Omit other fields ...
   components:
-   image: milvusdb/milvus:v2.5.18
+   image: milvusdb/milvus:v2.5.19
 ```
 
 Then run the following to perform the upgrade:
@@ -113,11 +113,11 @@ kubectl patch -f milvusupgrade.yaml --patch-file milvusupgrade.yaml --type merge
 
 ## Migrate the metadata
 
-Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus v2.5.18.
+Since Milvus 2.2.0, the metadata is incompatible with that in previous releases. The following example snippets assume an upgrade from Milvus 2.1.4 to Milvus v2.5.19.
 
 ### 1. Create a `.yaml` file for metadata migration
 
-Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.5.18`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.18.
+Create a metadata migration file. The following is an example. You need to specify the `name`, `sourceVersion`, and `targetVersion` in the configuration file. The following example sets the `name` to `my-release-upgrade`, `sourceVersion` to `v2.1.4`, and `targetVersion` to `v2.5.19`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.19.
 
 ```
 apiVersion: milvus.io/v1beta1
@@ -129,9 +129,9 @@ spec:
     namespace: default
     name: my-release
   sourceVersion: "v2.1.4"
-  targetVersion: "v2.5.18"
+  targetVersion: "v2.5.19"
   # below are some omit default values:
-  # targetImage: "milvusdb/milvus:v2.5.18"
+  # targetImage: "milvusdb/milvus:v2.5.19"
   # toolImage: "milvusdb/meta-migration:v2.2.0"
   # operation: upgrade
   # rollbackIfFailed: true