Merge remote-tracking branch 'origin/add-dataflow-docs' into add-dataflow-docs

Author: BentsiLeviav

.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

@@ -20,38 +20,43 @@ jobs:
   generate_toc_formats:
     runs-on: ubuntu-latest
     steps:
-      # Step 1: Check out the repository
+    
+      # Step 1 - Check out the repository
       - name: Check out repository
-        uses: actions/checkout@v3
-
-       # Step 2 - Setup Python
-      - name: Set up Python
-        uses: actions/setup-python@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@v5
         with:
           python-version: '3.x'
 
-      # Step 3: Install Python dependencies
+      # Step 4 - Install python dependencies
       - name: Install dependencies
         run: |
           python -m pip install --upgrade pip
           pip install -r 'scripts/table-of-contents-generator/requirements.txt'
 
-      # Step 4 -  Pull main repo docs, run script to generate TOCs:
-      - name: Generate TOCs
+      # Step 5 -  Pull main repo docs, run script to generate TOCs:
+      - name: Generate table of contents files
         run: |
           yarn prep-from-master
           python -u ./scripts/table-of-contents-generator/toc_gen.py --dir="docs/en/interfaces/formats" --single-toc --out="table-of-contents-files" --ignore "_snippets"
 
-      # Step 5 - Fail the workflow if script returns exit code 1
+      # Step 6 - Fail the workflow if script returns exit code 1
       - name: Check exit code
         run: |
           if [[ "${{ steps.toc_gen.outcome }}" == "failure" ]]; then
             echo "Ran into trouble generating a table of contents. See the logs for details."
             exit 1
           fi
 
-      # Step 6 - Check if anything was actually updated
-      - name: Check for Changes
+      # Step 7 - Check if anything was actually updated
+      - name: Check for changes
         id: check_changes
         run: |
           git status -u
@@ -63,7 +68,7 @@ jobs:
             echo "has_changes=false" >> $GITHUB_OUTPUT
           fi
 
-      # Step 7 - Commit and Push generated Table Of Contents files
+      # Step 8 - Commit and Push generated Table Of Contents files
       - uses: stefanzweifel/git-auto-commit-action@v5
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -28,6 +28,7 @@ clickhouse-docs.code-workspace
 yarn.lock
 yarn.error-log
 .comments
+yarn-error.log
 
 # Output files used by scripts to verify links
 sidebar_links.txt

docs/en/about-us/cloud.md

@@ -8,7 +8,7 @@ description: ClickHouse Cloud
 # ClickHouse Cloud
 
 ClickHouse Cloud is the cloud offering created by the original creators of the popular open-source OLAP database ClickHouse. 
-You can experience ClickHouse Cloud by [starting a free trial](https://clickhouse.cloud/signUp).
+You can experience ClickHouse Cloud by [starting a free trial](https://console.clickhouse.cloud/signUp).
 
 ### ClickHouse Cloud benefits:
 

docs/en/about-us/support.md

@@ -7,7 +7,7 @@ sidebar_position: 30
 
 ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our Support Services](https://clickhouse.com/support/program/) page.
 
-[Login to the Cloud console](https://clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
+[Login to the Cloud console](https://console.clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
 
 **Service level agreements ("SLA")**
 Classification of severity levels for issues reported and response times.

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/cloud-quick-start.md

@@ -10,13 +10,13 @@ import SQLConsoleDetail from '@site/docs/en/_snippets/_launch_sql_console.md';
 # ClickHouse Cloud Quick Start
 
 The quickest and easiest way to get up and running with ClickHouse is to create a new
-service in [ClickHouse Cloud](https://clickhouse.cloud).
+service in [ClickHouse Cloud](https://console.clickhouse.cloud).
 
 ## 1. Create a ClickHouse service 
 
-To create a free ClickHouse service in [ClickHouse Cloud](https://clickhouse.cloud), you just need to sign up by completing the following steps:
+To create a free ClickHouse service in [ClickHouse Cloud](https://console.clickhouse.cloud), you just need to sign up by completing the following steps:
 
-  - Create an account on the [sign-up page](https://clickhouse.cloud/signUp)
+  - Create an account on the [sign-up page](https://console.clickhouse.cloud/signUp)
   - You can choose to sign up using your email or via Google SSO, Microsoft SSO, AWS Marketplace, Google Cloud or Microsoft Azure
   - If you sign up using an email and password, remember to verify your email address within the next 24h via the link you receive in your email
   - Login using the username and password you just created

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/api/api-overview.md

@@ -29,4 +29,4 @@ The ClickHouse Cloud API is built on the open-source [OpenAPI specification](htt
 
 ## Support
 
-We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://clickhouse.cloud/support
+We recommend visiting [our Slack channel](https://clickhouse.com/slack) first to get quick support. If you'd like additional help or more info about our API and its capabilities, please contact ClickHouse Support at https://console.clickhouse.cloud/support