Skip to content

Commit f55f837

Browse files
Milvus-doc-botMilvus-doc-bot
Milvus-doc-bot
authored and
Milvus-doc-bot
committed
Release new docs to master
1 parent 0303b91 commit f55f837

22 files changed

+128
-99
lines changed

‎v2.6.x/Variables.json‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
{
2-
"milvus_release_version": "2.6.4",
3-
"milvus_release_tag": "2.6.4",
2+
"milvus_release_version": "2.6.5",
3+
"milvus_release_tag": "2.6.5",
44
"milvus_deb_amd64": "milvus_2.6.0-1_amd64.deb",
55
"milvus_rpm_amd64": "milvus_2.6.0-1_amd64.rpm",
66
"milvus_deb_arm64": "milvus_2.6.0-1_arm64.deb",
77
"milvus_rpm_arm64": "milvus_2.6.0-1_arm64.rpm",
88
"milvus_python_sdk_version": "2.4.x",
99
"milvus_python_sdk_real_version": "2.6.3",
1010
"milvus_node_sdk_version": "2.4.x",
11-
"milvus_node_sdk_real_version": "2.6.1",
11+
"milvus_node_sdk_real_version": "2.6.4",
1212
"milvus_go_sdk_version": "2.3.x",
1313
"milvus_go_sdk_real_version": "2.6.1",
1414
"milvus_java_sdk_version": "2.4.x",
15-
"milvus_java_sdk_real_version": "2.6.6",
15+
"milvus_java_sdk_real_version": "2.6.7",
1616
"milvus_csharp_sdk_version": "2.2.x",
1717
"milvus_csharp_sdk_real_version": "2.2.14",
1818
"milvus_restful_sdk_version": "2.4.x",

‎v2.6.x/site/en/adminGuide/configure-docker.md‎

Lines changed: 4 additions & 4 deletions
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.6.4/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
19+
[Download](https://raw.githubusercontent.com/milvus-io/milvus/v2.6.5/configs/milvus.yaml) `milvus.yaml` directly or with the following command.
2020

2121
```
22-
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.6.4/configs/milvus.yaml
22+
$ wget https://raw.githubusercontent.com/milvus-io/milvus/v2.6.5/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.6.4/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.6.5/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.6.4/milvus-standalone-docker-compose.yml -O docker-compose.yml
187+
$ wget https://github.com/milvus-io/milvus/releases/download/v2.6.5/milvus-standalone-docker-compose.yml -O docker-compose.yml
188188
```
189189

190190
## Modify the installation file

‎v2.6.x/site/en/adminGuide/deploy_pulsar.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ You can configure Pulsar with [Docker Compose](https://docs.docker.com/get-start
1313

1414
<div class="alert note">
1515

16-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
16+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
1717

1818

1919
</div>

‎v2.6.x/site/en/adminGuide/message_storage_operator.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ There are also other limitations for specifying the message storage:
3636
- Nats introduced in 2.3 do not participate in these priority rules for backward compatibility.
3737
- The message storage cannot be changed while the Milvus system is running.
3838
- Only Kafka 2.x or 3.x verison is supported.
39-
- **Upgrade limitations**: **Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
39+
- **Upgrade limitations**: **Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
4040

4141

4242
## Configure RocksMQ

‎v2.6.x/site/en/adminGuide/operator.md‎

Lines changed: 1 addition & 1 deletion
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.6.4/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.6.5/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.6.x/site/en/adminGuide/upgrade_milvus_cluster-docker.md‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ 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.6.4.
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.6.5.
1414

1515
<div class="alert note">
1616

17-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
17+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
1818

1919

2020
</div>
@@ -31,35 +31,35 @@ In normal cases, you can upgrade Milvus as follows:
3131
...
3232
rootcoord:
3333
container_name: milvus-rootcoord
34-
image: milvusdb/milvus:v2.6.4
34+
image: milvusdb/milvus:v2.6.5
3535
...
3636
proxy:
3737
container_name: milvus-proxy
38-
image: milvusdb/milvus:v2.6.4
38+
image: milvusdb/milvus:v2.6.5
3939
...
4040
querycoord:
4141
container_name: milvus-querycoord
42-
image: milvusdb/milvus:v2.6.4
42+
image: milvusdb/milvus:v2.6.5
4343
...
4444
querynode:
4545
container_name: milvus-querynode
46-
image: milvusdb/milvus:v2.6.4
46+
image: milvusdb/milvus:v2.6.5
4747
...
4848
indexcoord:
4949
container_name: milvus-indexcoord
50-
image: milvusdb/milvus:v2.6.4
50+
image: milvusdb/milvus:v2.6.5
5151
...
5252
indexnode:
5353
container_name: milvus-indexnode
54-
image: milvusdb/milvus:v2.6.4
54+
image: milvusdb/milvus:v2.6.5
5555
...
5656
datacoord:
5757
container_name: milvus-datacoord
58-
image: milvusdb/milvus:v2.6.4
58+
image: milvusdb/milvus:v2.6.5
5959
...
6060
datanode:
6161
container_name: milvus-datanode
62-
image: milvusdb/milvus:v2.6.4
62+
image: milvusdb/milvus:v2.6.5
6363
```
6464
6565
2. Run the following commands to perform the upgrade.
@@ -87,7 +87,7 @@ In normal cases, you can upgrade Milvus as follows:
8787
runWithBackup: true
8888
config:
8989
sourceVersion: 2.1.4 # Specify your milvus version
90-
targetVersion: 2.6.4
90+
targetVersion: 2.6.5
9191
backupFilePath: /tmp/migration.bak
9292
metastore:
9393
type: etcd

‎v2.6.x/site/en/adminGuide/upgrade_milvus_cluster-helm.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ title: Upgrade Milvus Cluster with Helm Chart
1212

1313
# Upgrade Milvus Cluster with Helm Chart
1414

15-
This guide describes how to upgrade your Milvus cluster from v2.5.x to v2.6.4 using Helm Chart.
15+
This guide describes how to upgrade your Milvus cluster from v2.5.x to v2.6.5 using Helm Chart.
1616

1717
## Before you start
1818

19-
### What's new in v2.6.4
19+
### What's new in v2.6.5
2020

21-
Upgrading from Milvus 2.5.x to 2.6.4 involves significant architectural changes:
21+
Upgrading from Milvus 2.5.x to 2.6.5 involves significant architectural changes:
2222

2323
- **Coordinator consolidation**: Legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`
2424
- **New components**: Introduction of Streaming Node for enhanced data processing
@@ -34,11 +34,11 @@ This upgrade process ensures proper migration to the new architecture. For more
3434
- Milvus cluster deployed via Helm Chart
3535

3636
**Compatibility requirements:**
37-
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.4. Direct upgrades from release candidates are not supported.
37+
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.5. Direct upgrades from release candidates are not supported.
3838
- If you are currently running v2.6.0-rc1 and need to preserve your data, please refer to [this community guide](https://github.com/milvus-io/milvus/issues/43538#issuecomment-3112808997) for migration assistance.
39-
- You **must** upgrade to v2.5.16 or later with `mixCoordinator` enabled before upgrading to v2.6.4.
39+
- You **must** upgrade to v2.5.16 or later with `mixCoordinator` enabled before upgrading to v2.6.5.
4040

41-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
41+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
4242

4343

4444
<div class="alert note">
@@ -110,13 +110,13 @@ Wait for the upgrade to complete:
110110
kubectl get pods
111111
```
112112

113-
### Step 3: Upgrade to v2.6.4
113+
### Step 3: Upgrade to v2.6.5
114114

115-
Once v2.5.16 is running successfully with `mixCoordinator`, upgrade to v2.6.4:
115+
Once v2.5.16 is running successfully with `mixCoordinator`, upgrade to v2.6.5:
116116

117117
```bash
118118
helm upgrade my-release zilliztech/milvus \
119-
--set image.all.tag="v2.6.4" \
119+
--set image.all.tag="v2.6.5" \
120120
--set streaming.enabled=true \
121121
--set indexNode.enabled=false \
122122
--reset-then-reuse-values \

‎v2.6.x/site/en/adminGuide/upgrade_milvus_cluster-operator.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ title: Upgrade Milvus Cluster with Milvus Operator
1212

1313
# Upgrade Milvus Cluster with Milvus Operator
1414

15-
This guide describes how to upgrade your Milvus cluster from v2.5.x to v2.6.4 using Milvus Operator.
15+
This guide describes how to upgrade your Milvus cluster from v2.5.x to v2.6.5 using Milvus Operator.
1616

1717
## Before you start
1818

19-
### What's new in v2.6.4
19+
### What's new in v2.6.5
2020

21-
Upgrading from Milvus 2.5.x to 2.6.4 involves significant architectural changes:
21+
Upgrading from Milvus 2.5.x to 2.6.5 involves significant architectural changes:
2222

2323
- **Coordinator consolidation**: Legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`
2424
- **New components**: Introduction of Streaming Node for enhanced data processing
@@ -34,11 +34,11 @@ This upgrade process ensures proper migration to the new architecture. For more
3434
- Helm 3.x installed
3535

3636
**Compatibility requirements:**
37-
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.4. Direct upgrades from release candidates are not supported.
37+
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.5. Direct upgrades from release candidates are not supported.
3838
- If you are currently running v2.6.0-rc1 and need to preserve your data, please refer to [this community guide](https://github.com/milvus-io/milvus/issues/43538#issuecomment-3112808997) for migration assistance.
39-
- You **must** upgrade to v2.5.16 or later with `mixCoord` enabled before upgrading to v2.6.4.
39+
- You **must** upgrade to v2.5.16 or later with `mixCoord` enabled before upgrading to v2.6.5.
4040

41-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
41+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
4242

4343

4444
## Upgrade process
@@ -106,9 +106,9 @@ Wait for completion:
106106
kubectl get pods
107107
```
108108

109-
#### 2.3 Upgrade to v2.6.4
109+
#### 2.3 Upgrade to v2.6.5
110110

111-
Once v2.5.16 is running successfully with `mixCoord`, upgrade to v2.6.4:
111+
Once v2.5.16 is running successfully with `mixCoord`, upgrade to v2.6.5:
112112

113113
Update your configuration file (`milvusupgrade.yaml` in this example):
114114

@@ -119,7 +119,7 @@ metadata:
119119
name: my-release # Replace with your actual release name
120120
spec:
121121
components:
122-
image: milvusdb/milvus:v2.6.4
122+
image: milvusdb/milvus:v2.6.5
123123
```
124124
125125
Apply the final upgrade:

‎v2.6.x/site/en/adminGuide/upgrade_milvus_standalone-docker.md‎

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,13 @@ title: Upgrade Milvus Standalone with Docker Compose
1212

1313
# Upgrade Milvus Standalone with Docker Compose
1414

15-
This guide describes how to upgrade your Milvus standalone deployment from v2.5.x to v2.6.4 using Docker Compose.
15+
This guide describes how to upgrade your Milvus standalone deployment from v2.5.x to v2.6.5 using Docker Compose.
1616

1717
## Before you start
1818

19-
### What's new in v2.6.4
19+
### What's new in v2.6.5
2020

21-
Upgrading from Milvus 2.5.x to 2.6.4 involves significant architectural changes:
21+
Upgrading from Milvus 2.5.x to 2.6.5 involves significant architectural changes:
2222

2323
- **Coordinator consolidation**: Legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`
2424
- **New components**: Introduction of Streaming Node for enhanced data processing
@@ -33,16 +33,16 @@ This upgrade process ensures proper migration to the new architecture. For more
3333
- Milvus standalone deployed via Docker Compose
3434

3535
**Compatibility requirements:**
36-
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.4. Direct upgrades from release candidates are not supported.
36+
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.5. Direct upgrades from release candidates are not supported.
3737
- If you are currently running v2.6.0-rc1 and need to preserve your data, please refer to [this community guide](https://github.com/milvus-io/milvus/issues/43538#issuecomment-3112808997) for migration assistance.
38-
- You **must** upgrade to v2.5.16 or later before upgrading to v2.6.4.
38+
- You **must** upgrade to v2.5.16 or later before upgrading to v2.6.5.
3939

40-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
40+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
4141

4242

4343
<div class="alter note">
4444

45-
Due to security concerns, Milvus upgrades its MinIO to RELEASE.2024-12-18T13-15-44Z with the release of v2.6.4.
45+
Due to security concerns, Milvus upgrades its MinIO to RELEASE.2024-12-18T13-15-44Z with the release of v2.6.5.
4646

4747
</div>
4848

@@ -79,9 +79,9 @@ Skip this step if your standalone deployment is already running v2.5.16 or highe
7979
docker compose ps
8080
```
8181

82-
### Step 2: Upgrade to v2.6.4
82+
### Step 2: Upgrade to v2.6.5
8383

84-
Once v2.5.16 is running successfully, upgrade to v2.6.4:
84+
Once v2.5.16 is running successfully, upgrade to v2.6.5:
8585

8686
1. Edit your existing `docker-compose.yaml` file and update both the Milvus and MinIO image tags:
8787

@@ -94,7 +94,7 @@ Once v2.5.16 is running successfully, upgrade to v2.6.4:
9494
...
9595
standalone:
9696
container_name: milvus-standalone
97-
image: milvusdb/milvus:v2.6.4
97+
image: milvusdb/milvus:v2.6.5
9898
```
9999

100100
2. Apply the final upgrade:

‎v2.6.x/site/en/adminGuide/upgrade_milvus_standalone-helm.md‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -13,13 +13,13 @@ title: Upgrade Milvus Standalone with Helm Chart
1313

1414
# Upgrade Milvus Standalone with Helm Chart
1515

16-
This guide describes how to upgrade your Milvus standalone deployment from v2.5.x to v2.6.4 using Helm Chart.
16+
This guide describes how to upgrade your Milvus standalone deployment from v2.5.x to v2.6.5 using Helm Chart.
1717

1818
## Before you start
1919

20-
### What's new in v2.6.4
20+
### What's new in v2.6.5
2121

22-
Upgrading from Milvus 2.5.x to 2.6.4 involves significant architectural changes:
22+
Upgrading from Milvus 2.5.x to 2.6.5 involves significant architectural changes:
2323

2424
- **Coordinator consolidation**: Legacy separate coordinators (`dataCoord`, `queryCoord`, `indexCoord`) have been consolidated into a single `mixCoord`
2525
- **New components**: Introduction of Streaming Node for enhanced data processing
@@ -35,11 +35,11 @@ This upgrade process ensures proper migration to the new architecture. For more
3535
- Milvus standalone deployed via Helm Chart
3636

3737
**Compatibility requirements:**
38-
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.4. Direct upgrades from release candidates are not supported.
38+
- Milvus v2.6.0-rc1 is **not compatible** with v2.6.5. Direct upgrades from release candidates are not supported.
3939
- If you are currently running v2.6.0-rc1 and need to preserve your data, please refer to [this community guide](https://github.com/milvus-io/milvus/issues/43538#issuecomment-3112808997) for migration assistance.
40-
- You **must** upgrade to v2.5.16 or later before upgrading to v2.6.4.
40+
- You **must** upgrade to v2.5.16 or later before upgrading to v2.6.5.
4141

42-
**Message Queue limitations**: When upgrading to Milvus v2.6.4, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
42+
**Message Queue limitations**: When upgrading to Milvus v2.6.5, you must maintain your current message queue choice. Switching between different message queue systems during the upgrade is not supported. Support for changing message queue systems will be available in future versions.
4343

4444

4545
<div class="alert note">
@@ -93,13 +93,13 @@ Wait for the upgrade to complete:
9393
kubectl get pods
9494
```
9595

96-
### Step 3: Upgrade to v2.6.4
96+
### Step 3: Upgrade to v2.6.5
9797

98-
Once v2.5.16 is running successfully, upgrade to v2.6.4:
98+
Once v2.5.16 is running successfully, upgrade to v2.6.5:
9999

100100
```bash
101101
helm upgrade my-release zilliztech/milvus \
102-
--set image.all.tag="v2.6.4" \
102+
--set image.all.tag="v2.6.5" \
103103
--reset-then-reuse-values \
104104
--version=5.0.0
105105
```

0 commit comments

Comments
 (0)