Merge branch 'main' into kb_tagged_search_mixed

Author: gingerwizard

.github/workflows/build-search.yml

@@ -21,10 +21,10 @@ jobs:
 
     steps:
       - name: Checkout Repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       - name: Set up Node.js
-        uses: actions/setup-node@v3
+        uses: actions/setup-node@v4
         with:
           node-version: '20' 
 

.github/workflows/check-build.yml

@@ -18,7 +18,7 @@ jobs:
     steps:
       # Step 1: Check out the repository
       - name: Check out repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       # Step 2: Set up environment if required (e.g., installing Aspell)
       - name: Install Aspell
@@ -33,7 +33,7 @@ jobs:
 
       # Step 4: Setup Python and dependencies for KB checker
       - name: Set up Python
-        uses: actions/setup-python@v3
+        uses: actions/setup-python@v5
         with:
           python-version: '3.x'
 

.github/workflows/table_of_contents.yml

@@ -23,15 +23,15 @@ jobs:
 
       # Step 1 - Check out the repository
       - name: Check out repository
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
 
       # Step 2 - Pull changes
       - name: Pull remote Changes
         run: git pull
 
       # Step 3 - Setup python
       - name: Set up python
-        uses: actions/setup-python@v3
+        uses: actions/setup-python@v5
         with:
           python-version: '3.x'
 

docs/en/cloud/bestpractices/usagelimits.md

@@ -4,28 +4,26 @@ sidebar_label: Usage Limits
 title: Usage Limits
 ---
 
-
-## Database Limits
-Clickhouse is very fast and reliable, but any database has its limits. For example, having too many tables or databases could negatively affect performance. To avoid that, Clickhouse Cloud has guardrails for several types of items.
+While ClickHouse is known for its speed and reliability, optimal performance is achieved within certain operating parameters. For example, having too many tables, databases or parts could negatively impact performance. To avoid this, Clickhouse Cloud has guardrails set up for several types of items. You can find details of these guardrails below.
 
 :::tip
-If you've reached one of those limits, it may mean that you are implementing your use case in an unoptimized way. You can contact our support so we can help you refine your use case to avoid going through the limits or to increase the limits in a guided way. 
+If you've run up against one of these guardrails, it's possible that you are implementing your use case in an unoptimized way. Contact our support team and we will gladly help you refine your use case to avoid exceeding the guardrails or look together at how we can increase them in a controlled manner. 
 :::
 
-# Tables
-Clickhouse Cloud have a limit of **5000** tables per instance
-
-# Databases
-Clickhouse Cloud have a limit of **1000** databases per instance
-
-# Partitions
-Clickhouse Cloud have a limit of **50000** [partitions](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key) per instance
-
-# Parts
-Clickhouse Cloud have a limit of **100000** [parts](https://clickhouse.com/docs/en/operations/system-tables/parts) per instance
+- **Databases**: 1000
+- **Tables**: 5000-10k
+- **Columns**: ∼1000 (wide format is preferred to compact)
+- **Partitions**: 50k
+- **Parts**: 100k across the entire instance
+- **Part size**: 150gb
+- **Services**: 20 (soft)
+- **Low cardinality**: 10k or less
+- **Primary keys in a table**: 4-5 that sufficiently filter down the data
+- **Concurrency**: default 100, can be increased to 1000 per node
+- **Batch ingest**: anything > 1M will be split by the system in 1M row blocks
 
 :::note
-For Single Replica Services, the maximum number of Databases is restricted to 100, and the maximum number of Tables is restricted to 500. In addition, Storage for Basic Tier Services is limited to 1 TB.
+For Single Replica Services, the maximum number of databases is restricted to 100, and the maximum number of tables is restricted to 500. In addition, storage for Basic Tier Services is limited to 1 TB.
 :::
 
 

docs/en/cloud/get-started/query-endpoints.md

@@ -5,12 +5,8 @@ description: Easily spin up REST API endpoints from your saved queries
 keywords: [api, query api endpoints, query endpoints, query rest api]
 ---
 
-import BetaBadge from '@theme/badges/BetaBadge';
-
 # Query API Endpoints
 
-<BetaBadge />
-
 The **Query API Endpoints** feature allows you to create an API endpoint directly from any saved SQL query in the ClickHouse Cloud console. You'll be able to access API endpoints via HTTP to execute your saved queries without needing to connect to your ClickHouse Cloud service via a native driver.
 
 ## Quick-start Guide

docs/en/cloud/manage/backups/export-backups-to-own-cloud-account.md

@@ -96,6 +96,10 @@ See: [Configuring BACKUP/RESTORE to use an S3 Endpoint](/docs/en/operations/back
 
 ## Backup / Restore to Azure Blob Storage
 
+:::note
+Exporting backups to you own bucket on Azure Blob Storage is not available yet. We will update this page when the feature is available.
+:::
+
 ### Take a DB Backup
 
 **Full Backup**

docs/en/cloud/manage/jan2025_faq/dimensions.md

@@ -49,13 +49,13 @@ It consists of two dimensions:
 
 ### How does it look in an illustrative example?
 
-For example, ingesting 1 TB of data over 24 hours using the Kafka connector using a single replica (0.5 compute unit) will cost:
+For example, ingesting 1 TB of data over 24 hours using the Kafka connector using a single replica (0.25 compute unit) will cost:
 
-`0.5 x 0.20 x 24 + 0.04 x 1000 = $42.4`
+`0.25 x 0.20 x 24 + 0.04 x 1000 = $41.2`
 
 For object storage connectors (S3 and GCS), only the ClickPipes compute cost is incurred since the ClickPipes pod is not processing data but only orchestrating the transfer, which is operated by the underlying ClickHouse service: 
 
-`0.5 x 0.20 x 24 = $2.4`
+`0.25 x 0.20 x 24 = $1.2`
 
 ### When does the new pricing model take effect?
 

docs/en/cloud/manage/scaling.md

@@ -73,7 +73,7 @@ However, these services can be scaled vertically by contacting support.
 
 You can use ClickHouse Cloud [public APIs](https://clickhouse.com/docs/en/cloud/manage/api/swagger#/paths/~1v1~1organizations~1:organizationId~1services~1:serviceId~1scaling/patch) to scale your service by updating the scaling settings for the service or adjust the number of replicas from the cloud console.
 
-A **Scale** or **Enterprise** ClickHouse service must have a minimum of `2` replicas.
+**Scale** and **Enterprise** tiers do support single-replica services. However, a service in these tiers that starts with multiple replicas, or scales out to multiples replicas can only be scaled back in to a minimum of `2` replicas.
 
 :::note
 Services can scale horizontally to a maximum of 20 replicas. If you need additional replicas, please contact our support team.