From ea0a46e988ca04cc6d5fd9db3669b04ebf1ff299 Mon Sep 17 00:00:00 2001 From: Milvus-doc-bot Date: Mon, 23 Dec 2024 12:30:12 +0000 Subject: [PATCH] Release new docs to master --- v2.5.x/Variables.json | 4 +-- v2.5.x/site/en/adminGuide/configure-docker.md | 8 +++--- v2.5.x/site/en/adminGuide/operator.md | 2 +- .../upgrade_milvus_cluster-docker.md | 20 ++++++------- .../adminGuide/upgrade_milvus_cluster-helm.md | 10 +++---- .../upgrade_milvus_cluster-operator.md | 20 ++++++------- .../upgrade_milvus_standalone-docker.md | 6 ++-- .../upgrade_milvus_standalone-helm.md | 28 +++++++++---------- .../upgrade_milvus_standalone-operator.md | 20 ++++++------- .../install_standalone-docker-compose.md | 2 +- .../install_standalone-docker-compose-gpu.md | 4 +-- v2.5.x/site/en/release_notes.md | 20 ++++++++++--- 12 files changed, 78 insertions(+), 66 deletions(-) diff --git a/v2.5.x/Variables.json b/v2.5.x/Variables.json index dd35e9cfe..8ccd4da5e 100644 --- a/v2.5.x/Variables.json +++ b/v2.5.x/Variables.json @@ -1,6 +1,6 @@ { - "milvus_release_version": "2.5.0-beta", - "milvus_release_tag": "2.5.0-beta", + "milvus_release_version": "2.5.0", + "milvus_release_tag": "2.5.0", "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", diff --git a/v2.5.x/site/en/adminGuide/configure-docker.md b/v2.5.x/site/en/adminGuide/configure-docker.md index cf86b5b98..bfcb2d218 100644 --- a/v2.5.x/site/en/adminGuide/configure-docker.md +++ b/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.0-beta/configs/milvus.yaml) `milvus.yaml` directly or with the following command. +[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.5.0/configs/milvus.yaml) `milvus.yaml` directly or with the following command. ``` -$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.0-beta/configs/milvus.yaml +$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.0/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.0-beta/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.0/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.0-beta/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose.yml -O docker-compose.yml ``` ## Modify the installation file diff --git a/v2.5.x/site/en/adminGuide/operator.md b/v2.5.x/site/en/adminGuide/operator.md index d661376c9..63b17afd9 100644 --- a/v2.5.x/site/en/adminGuide/operator.md +++ b/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. -
See Deploy Milvus Operator for more information.
+
See Deploy Milvus Operator for more information.
You need to specify a configuration file for using Milvus Operator to start a Milvus cluster. diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md index 04ce37eaf..a3f8d7dad 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md +++ b/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.0-beta. +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.0. ## 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.0-beta + image: milvusdb/milvus:v2.5.0 ... proxy: container_name: milvus-proxy - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... querycoord: container_name: milvus-querycoord - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... querynode: container_name: milvus-querynode - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... indexcoord: container_name: milvus-indexcoord - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... indexnode: container_name: milvus-indexnode - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... datacoord: container_name: milvus-datacoord - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ... datanode: container_name: milvus-datanode - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + targetVersion: 2.5.0 backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md index f7ccd4cbf..0f2d654e1 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md +++ b/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: -
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0-beta.
+
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0-beta. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0-beta. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
@@ -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.0-beta. +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.0. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0-beta -w 'milvusdb/milvus:v2.5.0-beta' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0 -w 'milvusdb/milvus:v2.5.0' ```
diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md index ec4a3ae5f..4a8293392 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md +++ b/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.0-beta, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0-beta, 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.0-beta, 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.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0, 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.0, 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` Then run the following to perform the upgrade: @@ -112,11 +112,11 @@ kubectl patch -f milvusupgrade.yaml ## 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.0-beta. +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.0. ### 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.0-beta`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.0-beta. +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.0`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.0. ``` apiVersion: milvus.io/v1beta1 @@ -128,9 +128,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.5.0-beta" + targetVersion: "v2.5.0" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.5.0-beta" + # targetImage: "milvusdb/milvus:v2.5.0" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md index f2ffa97b1..8edbda5d7 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md +++ b/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.0-beta. +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.0.
@@ -32,7 +32,7 @@ In normal cases, you can upgrade Milvus as follows: ... standalone: container_name: milvus-standalone - image: milvusdb/milvus:v2.5.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + targetVersion: 2.5.0 backupFilePath: /tmp/migration.bak metastore: type: etcd diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md index 554ec3a34..057ebe8b4 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md +++ b/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: -
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0-beta.
+
- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.
-- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0-beta. +- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0. -- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0-beta. +- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
@@ -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.0-beta. +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.0. ```shell -sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0-beta -w 'milvusdb/milvus:v2.5.0-beta' +sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0 -w 'milvusdb/milvus:v2.5.0' ```
@@ -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.0-beta +#### 2. Upgrade Milvus from v2.1.x to 2.5.0 -The following commands assume that you upgrade Milvus from v2.1.4 to 2.5.0-beta. Change them to the versions that fit your needs. +The following commands assume that you upgrade Milvus from v2.1.4 to 2.5.0. 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.0-beta + ./migrate.sh -i my-release -s 2.1.4 -t 2.5.0 ``` 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.0-beta + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 ``` 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.0-beta -r by-dev + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -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.0-beta -r by-dev -w milvusdb/milvus:v2.5.0-beta + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -r by-dev -w milvusdb/milvus:v2.5.0 ``` 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.0-beta -w milvusdb/milvus:v2.5.0-beta -d true + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -w milvusdb/milvus:v2.5.0 -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.0-beta -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.0-beta -r by-dev -o migrate -w milvusdb/milvus:v2.5.0-beta + ./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -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.0 -r by-dev -o migrate -w milvusdb/milvus:v2.5.0 diff --git a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md b/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md index 3e6ddfd5d..51750e7d9 100644 --- a/v2.5.x/site/en/adminGuide/upgrade_milvus_standalone-operator.md +++ b/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.0-beta, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). -- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0-beta, 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.0-beta, 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.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade). +- To upgrade Milvus from a minor release before v2.2.3 to 2.5.0, 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.0, 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` 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.0-beta + image: milvusdb/milvus:v2.5.0 ``` Then run the following to perform the upgrade: @@ -113,11 +113,11 @@ kubectl patch -f milvusupgrade.yaml ## 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.0-beta. +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.0. ### 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.0-beta`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.0-beta. +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.0`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.0. ``` apiVersion: milvus.io/v1beta1 @@ -129,9 +129,9 @@ spec: namespace: default name: my-release sourceVersion: "v2.1.4" - targetVersion: "v2.5.0-beta" + targetVersion: "v2.5.0" # below are some omit default values: - # targetImage: "milvusdb/milvus:v2.5.0-beta" + # targetImage: "milvusdb/milvus:v2.5.0" # toolImage: "milvusdb/meta-migration:v2.2.0" # operation: upgrade # rollbackIfFailed: true diff --git a/v2.5.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md b/v2.5.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md index 6894f74cc..e5cb0e4a7 100644 --- a/v2.5.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md +++ b/v2.5.x/site/en/getstarted/run-milvus-docker/install_standalone-docker-compose.md @@ -21,7 +21,7 @@ Milvus provides a Docker Compose configuration file in the Milvus repository. To ```shell # Download the configuration file -$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0-beta/milvus-standalone-docker-compose.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose.yml -O docker-compose.yml # Start Milvus $ sudo docker compose up -d diff --git a/v2.5.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md b/v2.5.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md index 0232e5c1e..69e6dfe1c 100644 --- a/v2.5.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md +++ b/v2.5.x/site/en/getstarted/run-milvus-gpu/install_standalone-docker-compose-gpu.md @@ -27,10 +27,10 @@ To install Milvus with GPU support using Docker Compose, follow these steps. ### 1. Download and configure the YAML file -Download [`milvus-standalone-docker-compose-gpu.yml`](https://github.com/milvus-io/milvus/releases/download/v2.5.0-beta/milvus-standalone-docker-compose-gpu.yml) and save it as docker-compose.yml manually, or with the following command. +Download [`milvus-standalone-docker-compose-gpu.yml`](https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose-gpu.yml) and save it as docker-compose.yml manually, or with the following command. ```shell -$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0-beta/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml +$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose-gpu.yml -O docker-compose.yml ``` You need to make some changes to the environment variables of the standalone service in the YAML file as follows: diff --git a/v2.5.x/site/en/release_notes.md b/v2.5.x/site/en/release_notes.md index 3027c9c09..29b9d84eb 100644 --- a/v2.5.x/site/en/release_notes.md +++ b/v2.5.x/site/en/release_notes.md @@ -8,15 +8,15 @@ 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.5.0 in this section. We suggest that you regularly visit this page to learn about updates. -## v2.5.0-beta +## v2.5.0 -Release date: November 26, 2024 +Release date: December 23, 2024 | Milvus version | Python SDK version | Node.js SDK version | Java SDK version | |----------------|--------------------|---------------------|------------------| -| 2.5.0-beta | 2.5.0 | 2.5.0 | 2.5.0 | +| 2.5.0 | 2.5.1 | 2.5.2 | 2.5.2 | -Milvus 2.5.0-beta brings significant advancements to enhance usability, scalability, and performance for users dealing with vector search and large-scale data management. With this release, Milvus integrates powerful new features like term-based search, clustering compaction for optimized queries, and versatile support for sparse and dense vector search methods. Enhancements in cluster management, indexing, and data handling introduce new levels of flexibility and ease of use, making Milvus an even more robust and user-friendly vector database. +Milvus 2.5.0 brings significant advancements to enhance usability, scalability, and performance for users dealing with vector search and large-scale data management. With this release, Milvus integrates powerful new features like term-based search, clustering compaction for optimized queries, and versatile support for sparse and dense vector search methods. Enhancements in cluster management, indexing, and data handling introduce new levels of flexibility and ease of use, making Milvus an even more robust and user-friendly vector database. ### Key Features @@ -125,3 +125,15 @@ Optimized the concurrency performance of Data Definition Language (DDL) operatio #### RESTful API Feature Alignment Aligned the functionalities of the RESTful API with other SDKs for consistency. + +#### Security & Configuration Updates + +Supported TLS to secure inter-node communication in more complex or enterprise environments. For details, refer to [Security Configuration](tls.md). + +#### Compaction Performance Enhancements + +Removed maximum segment limitations in mixed compaction and now prioritizes smaller segments first, improving efficiency and speeding up queries on large or fragmented datasets. + +#### Score-Based Channel Balancing + +Introduced a policy that dynamically balances loads across channels, enhancing resource utilization and overall stability in large-scale deployments.