From 9df54a3d2b3cf7eea3ebdd9db8b6dd9686b8198a Mon Sep 17 00:00:00 2001 From: Milvus-doc-bot Date: Thu, 19 Sep 2024 02:15:21 +0000 Subject: [PATCH] Generate en docs --- .../clouds/openshift/openshift.json | 2 +- .../adminGuide/clouds/openshift/openshift.md | 20 +++++++++---------- .../search-query-get/with-iterators.md | 6 +++--- 3 files changed, 14 insertions(+), 14 deletions(-) diff --git a/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.json b/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.json index 398a0e176..6c217a592 100644 --- a/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.json +++ b/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.json @@ -1 +1 @@ -{"codeList":["# milvus-operator-certificate.yaml\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\nname: milvus-operator-serving-cert\nnamespace: milvus-operator\nspec:\ndnsNames:\n- milvus-operator-webhook-service.milvus-operator.svc\n- milvus-operator-webhook-service.milvus-operator.svc.cluster.local\nissuerRef:\n kind: Issuer\n name: milvus-operator-selfsigned-issuer\nsecretName: milvus-operator-webhook-cert\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\nname: milvus-operator-selfsigned-issuer\nnamespace: milvus-operator\nspec:\nselfSigned: {}\n","kubectl apply -f milvus-operator-certificate.yaml\n","helm repo add milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update milvus-operator\n","helm -n milvus-operator upgrade --install --create-namespace milvus-operator milvus-operator/milvus-operator\n"],"headingContent":"Deploy a Milvus Cluster on OpenShift","anchorList":[{"label":"Deploy a Milvus Cluster on OpenShift","href":"Deploy-a-Milvus-Cluster-on-OpenShift","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Step 1: Install Cert Manager","href":"Step-1-Install-Cert-Manager","type":2,"isActive":false},{"label":"Step 2: Issue a Self-Signed Certificate for Milvus Operator","href":"Step-2-Issue-a-Self-Signed-Certificate-for-Milvus-Operator","type":2,"isActive":false},{"label":"Step 3: Install Milvus Operator","href":"Step-3-Install-Milvus-Operator","type":2,"isActive":false},{"label":"Step 4: Deploy Milvus","href":"Step-4-Deploy-Milvus","type":2,"isActive":false},{"label":"What's Next","href":"Whats-Next","type":2,"isActive":false}]} \ No newline at end of file +{"codeList":["# milvus-operator-certificate.yaml\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\n name: milvus-operator-serving-cert\n namespace: milvus-operator\nspec:\n dnsNames:\n - milvus-operator-webhook-service.milvus-operator.svc\n - milvus-operator-webhook-service.milvus-operator.svc.cluster.local\n issuerRef:\n kind: Issuer\n name: milvus-operator-selfsigned-issuer\n secretName: milvus-operator-webhook-cert\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n name: milvus-operator-selfsigned-issuer\n namespace: milvus-operator\nspec:\n selfSigned: {}\n","kubectl apply -f milvus-operator-certificate.yaml\n","helm repo add milvus-operator https://zilliztech.github.io/milvus-operator/\nhelm repo update milvus-operator\n","helm -n milvus-operator upgrade --install --create-namespace milvus-operator milvus-operator/milvus-operator\n"],"headingContent":"Deploy a Milvus Cluster on OpenShift","anchorList":[{"label":"Deploy a Milvus Cluster on OpenShift","href":"Deploy-a-Milvus-Cluster-on-OpenShift","type":1,"isActive":false},{"label":"Prerequisites","href":"Prerequisites","type":2,"isActive":false},{"label":"Step 1: Install Cert Manager","href":"Step-1-Install-Cert-Manager","type":2,"isActive":false},{"label":"Step 2: Issue a Self-Signed Certificate for Milvus Operator","href":"Step-2-Issue-a-Self-Signed-Certificate-for-Milvus-Operator","type":2,"isActive":false},{"label":"Step 3: Install Milvus Operator","href":"Step-3-Install-Milvus-Operator","type":2,"isActive":false},{"label":"Step 4: Deploy Milvus","href":"Step-4-Deploy-Milvus","type":2,"isActive":false},{"label":"What's Next","href":"Whats-Next","type":2,"isActive":false}]} \ No newline at end of file diff --git a/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.md b/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.md index fb3c6e3e3..99b8d9b44 100644 --- a/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.md +++ b/localization/v2.4.x/site/en/adminGuide/clouds/openshift/openshift.md @@ -100,24 +100,24 @@ summary: Learn how to deploy a Milvus cluster on OpenShift. apiVersion: cert-manager.io/v1 kind: Certificate metadata: -name: milvus-operator-serving-cert -namespace: milvus-operator + name: milvus-operator-serving-cert + namespace: milvus-operator spec: -dnsNames: -- milvus-operator-webhook-service.milvus-operator.svc -- milvus-operator-webhook-service.milvus-operator.svc.cluster.local -issuerRef: + dnsNames: + - milvus-operator-webhook-service.milvus-operator.svc + - milvus-operator-webhook-service.milvus-operator.svc.cluster.local + issuerRef: kind: Issuer name: milvus-operator-selfsigned-issuer -secretName: milvus-operator-webhook-cert + secretName: milvus-operator-webhook-cert --- apiVersion: cert-manager.io/v1 kind: Issuer metadata: -name: milvus-operator-selfsigned-issuer -namespace: milvus-operator + name: milvus-operator-selfsigned-issuer + namespace: milvus-operator spec: -selfSigned: {} + selfSigned: {}

  • Apply the file:

    kubectl apply -f milvus-operator-certificate.yaml
diff --git a/localization/v2.4.x/site/en/userGuide/search-query-get/with-iterators.md b/localization/v2.4.x/site/en/userGuide/search-query-get/with-iterators.md
index e6420c2e9..0fff0fca9 100644
--- a/localization/v2.4.x/site/en/userGuide/search-query-get/with-iterators.md
+++ b/localization/v2.4.x/site/en/userGuide/search-query-get/with-iterators.md
@@ -21,7 +21,7 @@ title: With Iterators
           d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"
         >
       
-    
    Milvus provides search and query iterators for iterating results with a large volume of entities. Since Milvus limits TopK to 16384, users can use iterators to return large numbers or even whole entities in a collection in batch mode.
    
+    
    Milvus provides search and query iterators for iterating through a large volume of entities. Since Milvus limits TopK to 16384, users can use iterators to return large numbers or even whole entities in a collection in batch mode.
    
 
    Overview
    Iterators are powerful tools that help you iterate through a large volume of or all data within a collection using primary key values and Boolean expressions. This can significantly improve the way you retrieve data. Unlike the traditional use of offset and limit parameters, which may become less efficient over time, iterators offer a more scalable solution.
    
+    
    Iterators are efficient tool for scanning a whole collection or iterating through a large volume of entities by specifying primary key values or a filter expression. Compared to a search or query call with offset and limit parameters, using iterators is more efficient and scalable.
    
 
    Benefits of using iterators
      
 
    • Simplicity: Eliminates the complex offset and limit settings.
      • 
 
    • Efficiency: Provides scalable data retrieval by fetching only the data in need.
      • 
@@ -64,7 +64,7 @@ title: With Iterators
           d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"
         >
       
-    
      The following steps repurpose the code to connect to Milvus, quickly set up a collection, and insert over 10,000 randomly generated entities into the collection.
      
+    
      The following preparation step connects to Milvus and inserts randomly generated entities into a collection.
      
 
      Step 1: Create a collection
      
 
      Use MilvusClient to connect to the Milvus server and create_collection() to create a collection.