Merge pull request #2878 from liyun95/v2.5.x-preview

V2.5.x preview
milvus-io · Nov 26, 2024 · 755a500 · 755a500
2 parents e79bcb5 + 3908b68
commit 755a500
Show file tree

Hide file tree

Showing 100 changed files with 18,534 additions and 13,910 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -3,7 +3,7 @@ name: dev
 on:
   push:
     branches:
-      - v2.4.x
+      - v2.5.x-preview
   release:
     types: [released]
   workflow_dispatch:
@@ -20,7 +20,7 @@ jobs:
       - name: Check out Git repository
         uses: actions/checkout@v1
         with:
-          ref: v2.4.x
+          ref: v2.5.x-preview
 
       - name: Extract branch name
         shell: bash
@@ -52,4 +52,4 @@ jobs:
           cp -avr ../milvus-docs/** ./`cat version.json | jq -r .version`
           git add .
           git commit -m "Release new docs "
-          git push -f origin master
+          git push -f origin preview
diff --git a/assets/analyzer-overview.png b/assets/analyzer-overview.png
diff --git a/assets/ann-search.png b/assets/ann-search.png
diff --git a/assets/batch-data-and-streaming-data.png b/assets/batch-data-and-streaming-data.png
diff --git a/assets/binary-vector.png b/assets/binary-vector.png
diff --git a/assets/bitmap.png b/assets/bitmap.png
diff --git a/assets/bm25.png b/assets/bm25.png
diff --git a/assets/collection-explained.png b/assets/collection-explained.png
diff --git a/assets/consistency-level-illustrated.png b/assets/consistency-level-illustrated.png
diff --git a/assets/dense-vector.png b/assets/dense-vector.png
diff --git a/assets/filtered-search.png b/assets/filtered-search.png
diff --git a/assets/full-text-search.png b/assets/full-text-search.png
diff --git a/assets/grouping-search.png b/assets/grouping-search.png
diff --git a/assets/hybrid-search.png b/assets/hybrid-search.png
diff --git a/assets/idf.png b/assets/idf.png
diff --git a/assets/keyword-match.png b/assets/keyword-match.png
diff --git a/assets/partition-vs-partition-key.png b/assets/partition-vs-partition-key.png
diff --git a/assets/range-search.png b/assets/range-search.png
diff --git a/assets/schema-explained.PNG b/assets/schema-explained.PNG
diff --git a/assets/schema-hands-on.png b/assets/schema-hands-on.png
diff --git a/assets/service-time-and-guarantee-time.png b/assets/service-time-and-guarantee-time.png
diff --git a/assets/sparse-vector.png b/assets/sparse-vector.png
diff --git a/assets/upsert-entities.png b/assets/upsert-entities.png
diff --git a/assets/use-binary-vector.png b/assets/use-binary-vector.png
diff --git a/assets/use-dense-vector.png b/assets/use-dense-vector.png
diff --git a/assets/use-sparse-vector.png b/assets/use-sparse-vector.png
diff --git a/assets/with-and-without-partition-key.png b/assets/with-and-without-partition-key.png
diff --git a/site/en/about/overview.md b/site/en/about/overview.md
@@ -80,7 +80,7 @@ In addition to primitive data types, Milvus supports various advanced data types
 - [Sparse Vectors](sparse_vector.md)
 - [Binary Vectors](index-vector-fields.md)
 - [JSON Support](use-json-fields.md)
-- [Array Support](array_data_type.md)
+- [Array Support](array.md)
 - [Distance Metrics](metric.md)
 
 ### Acceleration

diff --git a/site/en/adminGuide/resource_group.md b/site/en/adminGuide/resource_group.md
@@ -56,7 +56,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     To create a resource group, run the following after you connect to a Milvus instance. The following snippet assumes that `default` is the alias of your Milvus connection.
 
-    ```Python
+    ```python
     import pymilvus
 
     # A resource group name should be a string of 1 to 255 characters, starting with a letter or an underscore (_) and containing only numbers, letters, and underscores (_).
@@ -80,7 +80,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     To view the list of resource groups in a Milvus instance, do as follows:
 
-    ```Python
+    ```python
     rgs = utility.list_resource_groups(using='default')
     print(f"Resource group list: {rgs}")
 
@@ -91,7 +91,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     You can have Milvus describe a resource group in concern as follows:
 
-    ```Python
+    ```python
     info = utility.describe_resource_group(name, using="default")
     print(f"Resource group description: {info}")
 
@@ -110,7 +110,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
     Assuming there are currently 1 QueryNodes in the **__default_resource_group** of the cluster, and we want to transfer one node into created **rg**.
     `update_resource_groups` ensures atomicity for multiple configuration changes, so no intermediate states will be visible to Milvus. 
 
-    ```Python
+    ```python
     source = '__default_resource_group'
     target = 'rg'
     expected_num_nodes_in_default = 0
@@ -138,7 +138,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     Once there are query nodes in a resource group, you can load collections to this resource group. The following snippet assumes that a collection named `demo` already exists.
 
-    ```Python
+    ```python
     from pymilvus import Collection
 
     collection = Collection('demo')
@@ -154,7 +154,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     Also, you can just load a partition into a resource group and have its replicas distributed among several resource groups. The following assumes that a collection named `Books` already exists and it has a partition named `Novels`.
 
-    ```Python
+    ```python
     collection = Collection("Books")
 
     # Use the load method of a collection to load one of its partition
@@ -173,7 +173,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     Milvus uses [replicas](replica.md) to achieve load-balancing among [segments](glossary.md#Segment) distributed across several query nodes. You can move certain replicas of a collection from one resource group to another as follows:
 
-    ```Python
+    ```python
     source = '__default_resource_group'
     target = 'rg'
     collection_name = 'c'
@@ -192,7 +192,7 @@ All code samples on this page are in PyMilvus {{var.milvus_python_sdk_real_versi
 
     You can drop a resource group that hold no query node (`limits.node_num = 0`) at any time. In this guide, resource group `rg` now has one query node. You need to change the configuration `limits.node_num` of resource group into zero first.
 
-    ```Python
+    ```python
     try:
         utility.update_resource_groups({
             "rg": utility.ResourceGroupConfig(
@@ -218,7 +218,7 @@ Here is a good practice for managing QueryNodes in a cloud environment:
     Additionally, if we strictly enforce the constraint `sum(.requests.nodeNum) <= queryNodeNum`, we can precisely control the assignment of QueryNodes in the cluster. Let's assume there is currently only one QueryNode in the cluster and initialize the cluster.
     Here is an example setup:
 
-    ```Python
+    ```python
     from pymilvus import utility
     from pymilvus.client.types import ResourceGroupConfig
 
@@ -261,15 +261,15 @@ Here is a good practice for managing QueryNodes in a cloud environment:
 2. Cluster scale out
 
     Assuming we have the following scaling function:
-    ```Python
+    ```python
 
     def scale_to(node_num: int):
         # scale the querynode number in Milvus into node_num.
         pass
     ```
 
     We can use the API to scale a specific resource group to a designated number of QueryNodes without affecting any other resource groups.
-    ```Python
+    ```python
     # scale rg1 into 3 nodes, rg2 into 1 nodes
     utility.update_resource_groups({
         "rg1": ResourceGroupConfig(
@@ -293,7 +293,7 @@ Here is a good practice for managing QueryNodes in a cloud environment:
 
     Similarly, we can establish scaling-in rules that prioritize selecting QueryNodes from **__pending_nodes** resource group. This information can be obtained through the `describe_resource_group` API. Achieving the goal of scaling-in specified resource group.
 
-    ```Python
+    ```python
     # scale rg1 from 3 nodes into 2 nodes
     utility.update_resource_groups({
         "rg1": ResourceGroupConfig(