Skip to content

Commit e2021f8

Browse files
Milvus-doc-botMilvus-doc-bot
Milvus-doc-bot
authored and
Milvus-doc-bot
committed
Release new docs to master
1 parent 6de27b8 commit e2021f8

14 files changed

+93
-65
lines changed

v2.5.x/Variables.json

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
{
2-
"milvus_release_version": "2.5.0",
3-
"milvus_release_tag": "2.5.0",
2+
"milvus_release_version": "2.5.1",
3+
"milvus_release_tag": "2.5.1",
44
"milvus_deb_name": "milvus_2.2.0-1_amd64",
55
"milvus_rpm_name": "milvus-2.2.0-1.el7.x86_64",
66
"milvus_python_sdk_version": "2.4.x",
7-
"milvus_python_sdk_real_version": "2.5.1",
7+
"milvus_python_sdk_real_version": "2.5.2",
88
"milvus_node_sdk_version": "2.4.x",
99
"milvus_node_sdk_real_version": "v2.5.2",
1010
"milvus_go_sdk_version": "2.3.x",

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

+4-4
Original file line numberDiff line numberDiff line change
@@ -16,10 +16,10 @@ In current release, all parameters take effect only after Milvus restarts.
1616

1717
## Download a configuration file
1818

19-
[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.5.0/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
19+
[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.5.1/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
2020

2121
```
22-
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.0/configs/milvus.yaml
22+
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.5.1/configs/milvus.yaml
2323
```
2424

2525
## Modify the configuration file
@@ -178,13 +178,13 @@ Sorted by:
178178

179179
## Download an installation file
180180

181-
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`.
181+
Download the installation file for Milvus [standalone](https://github.com/milvus-io/milvus/releases/download/v2.5.1/milvus-standalone-docker-compose.yml), and save it as `docker-compose.yml`.
182182

183183
You can also simply run the following command.
184184

185185
```
186186
# For Milvus standalone
187-
$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.0/milvus-standalone-docker-compose.yml -O docker-compose.yml
187+
$ wget https://github.com/milvus-io/milvus/releases/download/v2.5.1/milvus-standalone-docker-compose.yml -O docker-compose.yml
188188
```
189189

190190
## Modify the installation file

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Milvus cluster depends on components including object storage, etcd, and Pulsar.
1212

1313
This topic assumes that you have deployed Milvus Operator.
1414

15-
<div class="alert note">See <a href="https://milvus.io/docs/v2.5.0/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
15+
<div class="alert note">See <a href="https://milvus.io/docs/v2.5.1/install_cluster-milvusoperator.md">Deploy Milvus Operator</a> for more information. </div>
1616

1717
You need to specify a configuration file for using Milvus Operator to start a Milvus cluster.
1818

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

+1-1
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Of course, if the number of QueryNodes in the cluster changes, the Milvus will c
4848

4949
<div class="alert note">
5050

51-
All code samples on this page are in PyMilvus 2.5.1. Upgrade your PyMilvus installation before running them.
51+
All code samples on this page are in PyMilvus 2.5.2. Upgrade your PyMilvus installation before running them.
5252

5353
</div>
5454

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

+10-10
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ title: Upgrade Milvus Cluster with Docker Compose
1010

1111
This topic describes how to upgrade your Milvus using Docker Compose.
1212

13-
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.
13+
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.1.
1414

1515
## Upgrade Milvus by changing its image
1616

@@ -24,35 +24,35 @@ In normal cases, you can upgrade Milvus as follows:
2424
...
2525
rootcoord:
2626
container_name: milvus-rootcoord
27-
image: milvusdb/milvus:v2.5.0
27+
image: milvusdb/milvus:v2.5.1
2828
...
2929
proxy:
3030
container_name: milvus-proxy
31-
image: milvusdb/milvus:v2.5.0
31+
image: milvusdb/milvus:v2.5.1
3232
...
3333
querycoord:
3434
container_name: milvus-querycoord
35-
image: milvusdb/milvus:v2.5.0
35+
image: milvusdb/milvus:v2.5.1
3636
...
3737
querynode:
3838
container_name: milvus-querynode
39-
image: milvusdb/milvus:v2.5.0
39+
image: milvusdb/milvus:v2.5.1
4040
...
4141
indexcoord:
4242
container_name: milvus-indexcoord
43-
image: milvusdb/milvus:v2.5.0
43+
image: milvusdb/milvus:v2.5.1
4444
...
4545
indexnode:
4646
container_name: milvus-indexnode
47-
image: milvusdb/milvus:v2.5.0
47+
image: milvusdb/milvus:v2.5.1
4848
...
4949
datacoord:
5050
container_name: milvus-datacoord
51-
image: milvusdb/milvus:v2.5.0
51+
image: milvusdb/milvus:v2.5.1
5252
...
5353
datanode:
5454
container_name: milvus-datanode
55-
image: milvusdb/milvus:v2.5.0
55+
image: milvusdb/milvus:v2.5.1
5656
```
5757
5858
2. Run the following commands to perform the upgrade.
@@ -80,7 +80,7 @@ In normal cases, you can upgrade Milvus as follows:
8080
runWithBackup: true
8181
config:
8282
sourceVersion: 2.1.4 # Specify your milvus version
83-
targetVersion: 2.5.0
83+
targetVersion: 2.5.1
8484
backupFilePath: /tmp/migration.bak
8585
metastore:
8686
type: etcd

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

+5-5
Original file line numberDiff line numberDiff line change
@@ -85,11 +85,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope
8585

8686
You can choose the upgrade path for your Milvus as follows:
8787

88-
<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.</div>
88+
<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.1.</div>
8989

90-
- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0.
90+
- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.1.
9191

92-
- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
92+
- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.1.
9393

9494
<div style="display: none;">
9595

@@ -111,10 +111,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
111111
| `w` | New Milvus image tag | `milvusdb/milvus:v2.2.3` | True |
112112
| `o` | Operation | `update` | False |
113113

114-
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.
114+
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.1.
115115

116116
```shell
117-
sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0 -w 'milvusdb/milvus:v2.5.0'
117+
sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.1 -w 'milvusdb/milvus:v2.5.1'
118118
```
119119

120120
<div class="alert note">

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

+10-10
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu
2626

2727
Once you have upgraded your Milvus operator to the latest version, you have the following choices:
2828

29-
- To upgrade Milvus from v2.2.3 or later releases to 2.5.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30-
- 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).
31-
- To upgrade Milvus from v2.1.x to 2.5.0, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
29+
- To upgrade Milvus from v2.2.3 or later releases to 2.5.1, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30+
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.1, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31+
- To upgrade Milvus from v2.1.x to 2.5.1, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
3232

3333
## Conduct a rolling upgrade
3434

@@ -47,7 +47,7 @@ spec:
4747
components:
4848
enableRollingUpdate: true
4949
imageUpdateMode: rollingUpgrade # Default value, can be omitted
50-
image: milvusdb/milvus:v2.5.0
50+
image: milvusdb/milvus:v2.5.1
5151
```
5252
5353
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:
6363
components:
6464
enableRollingUpdate: true
6565
imageUpdateMode: all
66-
image: milvusdb/milvus:v2.5.0
66+
image: milvusdb/milvus:v2.5.1
6767
```
6868

6969
You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
@@ -101,7 +101,7 @@ metadata:
101101
spec:
102102
# Omit other fields ...
103103
components:
104-
image: milvusdb/milvus:v2.5.0
104+
image: milvusdb/milvus:v2.5.1
105105
```
106106

107107
Then run the following to perform the upgrade:
@@ -112,11 +112,11 @@ kubectl patch -f milvusupgrade.yaml
112112

113113
## Migrate the metadata
114114

115-
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.
115+
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.1.
116116

117117
### 1. Create a `.yaml` file for metadata migration
118118

119-
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.
119+
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.1`. This means that your Milvus cluster will be upgraded from v2.1.4 to v2.5.1.
120120

121121
```
122122
apiVersion: milvus.io/v1beta1
@@ -128,9 +128,9 @@ spec:
128128
namespace: default
129129
name: my-release
130130
sourceVersion: "v2.1.4"
131-
targetVersion: "v2.5.0"
131+
targetVersion: "v2.5.1"
132132
# below are some omit default values:
133-
# targetImage: "milvusdb/milvus:v2.5.0"
133+
# targetImage: "milvusdb/milvus:v2.5.1"
134134
# toolImage: "milvusdb/meta-migration:v2.2.0"
135135
# operation: upgrade
136136
# rollbackIfFailed: true

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

+3-3
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ title: Upgrade Milvus Standalone with Docker Compose
1414

1515
This topic describes how to upgrade your Milvus using Docker Compose.
1616

17-
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.
17+
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.1.
1818

1919
<div class="alter note">
2020

@@ -32,7 +32,7 @@ In normal cases, you can upgrade Milvus as follows:
3232
...
3333
standalone:
3434
container_name: milvus-standalone
35-
image: milvusdb/milvus:v2.5.0
35+
image: milvusdb/milvus:v2.5.1
3636
```
3737
3838
2. Run the following commands to perform the upgrade.
@@ -60,7 +60,7 @@ In normal cases, you can upgrade Milvus as follows:
6060
runWithBackup: true
6161
config:
6262
sourceVersion: 2.1.4 # Specify your milvus version
63-
targetVersion: 2.5.0
63+
targetVersion: 2.5.1
6464
backupFilePath: /tmp/migration.bak
6565
metastore:
6666
type: etcd

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

+14-14
Original file line numberDiff line numberDiff line change
@@ -86,11 +86,11 @@ zilliztech/milvus 4.1.0 2.3.0 Milvus is an ope
8686

8787
You can choose the upgrade path for your Milvus as follows:
8888

89-
<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.0.</div>
89+
<div style="display: none;">- [Conduct a rolling upgrade](#conduct-a-rolling-upgrade) from Milvus v2.2.3 and later releases to v2.5.1.</div>
9090

91-
- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.0.
91+
- [Upgrade Milvus using Helm](#Upgrade-Milvus-using-Helm) for an upgrade from a minor release before v2.2.3 to v2.5.1.
9292

93-
- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.0.
93+
- [Migrate the metadata](#Migrate-the-metadata) before the upgrade from Milvus v2.1.x to v2.5.1.
9494

9595
<div style="display:none;">
9696

@@ -112,10 +112,10 @@ The script applies only to the upgrade of Milvus installed with Helm. The follow
112112
| `w` | New Milvus image tag | `milvusdb/milvus:v2.2.3` | True |
113113
| `o` | Operation | `update` | False |
114114

115-
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.
115+
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.1.
116116

117117
```shell
118-
sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.0 -w 'milvusdb/milvus:v2.5.0'
118+
sh rollingUpdate.sh -n default -i my-release -o update -t 2.5.1 -w 'milvusdb/milvus:v2.5.1'
119119
```
120120

121121
<div class="alert note">
@@ -203,42 +203,42 @@ The following table lists the operations you can do for meta migration.
203203
4. Migrate the Milvus metadata.
204204
5. Start Milvus components with a new image.
205205

206-
#### 2. Upgrade Milvus from v2.1.x to 2.5.0
206+
#### 2. Upgrade Milvus from v2.1.x to 2.5.1
207207

208-
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.
208+
The following commands assume that you upgrade Milvus from v2.1.4 to 2.5.1. Change them to the versions that fit your needs.
209209

210210
1. Specify Milvus instance name, source Milvus version, and target Milvus version.
211211

212212
```
213-
./migrate.sh -i my-release -s 2.1.4 -t 2.5.0
213+
./migrate.sh -i my-release -s 2.1.4 -t 2.5.1
214214
```
215215
216216
2. Specify the namespace with `-n` if your Milvus is not installed in the default K8s namespace.
217217
218218
```
219-
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0
219+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1
220220
```
221221
222222
3. Specify the root path with `-r` if your Milvus is installed with the custom `rootpath`.
223223
224224
```
225-
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -r by-dev
225+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1 -r by-dev
226226
```
227227
228228
4. Specify the image tag with `-w` if your Milvus is installed with a custom `image`.
229229
230230
```
231-
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -r by-dev -w milvusdb/milvus:v2.5.0
231+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1 -r by-dev -w milvusdb/milvus:v2.5.1
232232
```
233233
234234
5. Set `-d true` if you want to automatically remove the migration pod after the migration is completed.
235235
236236
```
237-
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.0 -w milvusdb/milvus:v2.5.0 -d true
237+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1 -w milvusdb/milvus:v2.5.1 -d true
238238
```
239239
240240
6. Rollback and migrate again if the migration fails.
241241
242242
```
243-
./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
244-
./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
243+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1 -r by-dev -o rollback -w milvusdb/milvus:v2.1.1
244+
./migrate.sh -i my-release -n milvus -s 2.1.4 -t 2.5.1 -r by-dev -o migrate -w milvusdb/milvus:v2.5.1

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

+10-10
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,9 @@ helm -n milvus-operator upgrade milvus-operator zilliztech-milvus-operator/milvu
2626

2727
Once you have upgraded your Milvus operator to the latest version, you have the following choices:
2828

29-
- To upgrade Milvus from v2.2.3 or later releases to 2.5.0, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30-
- 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).
31-
- To upgrade Milvus from v2.1.x to 2.5.0, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
29+
- To upgrade Milvus from v2.2.3 or later releases to 2.5.1, you can [conduct a rolling upgrade](#Conduct-a-rolling-upgrade).
30+
- To upgrade Milvus from a minor release before v2.2.3 to 2.5.1, you are advised to [upgrade Milvus by changing its image version](#Upgrade-Milvus-by-changing-its-image).
31+
- To upgrade Milvus from v2.1.x to 2.5.1, you need to [migrate the metadata](#Migrate-the-metadata) before the actual upgrade.
3232

3333
## Conduct a rolling upgrade
3434

@@ -47,7 +47,7 @@ spec:
4747
components:
4848
enableRollingUpdate: true
4949
imageUpdateMode: rollingUpgrade # Default value, can be omitted
50-
image: milvusdb/milvus:v2.5.0
50+
image: milvusdb/milvus:v2.5.1
5151
```
5252
5353
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:
6363
components:
6464
enableRollingUpdate: true
6565
imageUpdateMode: all
66-
image: milvusdb/milvus:v2.5.0
66+
image: milvusdb/milvus:v2.5.1
6767
```
6868

6969
You can set `spec.components.imageUpdateMode` to `rollingDowngrade` to have Milvus replace coordinator pod images with a lower version.
@@ -102,7 +102,7 @@ labels:
102102
spec:
103103
# Omit other fields ...
104104
components:
105-
image: milvusdb/milvus:v2.5.0
105+
image: milvusdb/milvus:v2.5.1
106106
```
107107

108108
Then run the following to perform the upgrade:
@@ -113,11 +113,11 @@ kubectl patch -f milvusupgrade.yaml
113113

114114
## Migrate the metadata
115115

116-
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.
116+
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.1.
117117

118118
### 1. Create a `.yaml` file for metadata migration
119119

120-
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.
120+
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.1`. This means that your Milvus instance will be upgraded from v2.1.4 to v2.5.1.
121121

122122
```
123123
apiVersion: milvus.io/v1beta1
@@ -129,9 +129,9 @@ spec:
129129
namespace: default
130130
name: my-release
131131
sourceVersion: "v2.1.4"
132-
targetVersion: "v2.5.0"
132+
targetVersion: "v2.5.1"
133133
# below are some omit default values:
134-
# targetImage: "milvusdb/milvus:v2.5.0"
134+
# targetImage: "milvusdb/milvus:v2.5.1"
135135
# toolImage: "milvusdb/meta-migration:v2.2.0"
136136
# operation: upgrade
137137
# rollbackIfFailed: true

v2.5.x/site/en/getstarted/install_SDKs/install-pymilvus.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ It is recommended to install a PyMilvus version that matches the version of the
2727
</div>
2828

2929
```
30-
$ python3 -m pip install pymilvus==2.5.1
30+
$ python3 -m pip install pymilvus==2.5.2
3131
```
3232

3333
## Verify installation

0 commit comments

Comments
 (0)