Merge branch 'main' into add_query_condition_cache_to_sidebar

Author: Blargian

.github/workflows/build-search.yml

@@ -28,7 +28,7 @@ jobs:
           node-version: '20' 
 
       - name: Run Prep from Master
-        run: yarn copy-clickhouse-repo-docs
+        run: yarn copy-clickhouse-repo-docs -f
 
       - name: Run Auto Generate Settings
         run: yarn autogenerate-settings

docs/cloud/manage/billing/payment-thresholds.md

@@ -16,4 +16,4 @@ This payment threshold does not apply to customers who have a committed spend co
 
 If your organization reaches 90% of the payment threshold and is on-track to exceed the payment threshold mid-period, the billing email associated with the organization will receive an email notification. You will also receive an email notification as well as an invoice when you exceed the payment threshold.
 
-These payment thresholds can be adjusted. If you have any questions, please contact [email protected] for more details.
+These payment thresholds can be adjusted below $10,000 as requested by customers or by the ClickHouse Finance team. If you have any questions, please contact [email protected] for more details.

docs/cloud/manage/notifications.md

@@ -19,36 +19,30 @@ ClickHouse Cloud sends notifications about critical events related to your servi
 
 ## Receiving Notifications {#receiving-notifications}
 
-Notifications can be received via various channels. For now, ClickHouse Cloud supports receiving notifications through email and ClickHouse Cloud UI.  You can click on the bell icon in the top left menu to view current notifications, which opens a flyout. Clicking the button **View All** the bottom of the flyout will take you to a page that shows an activity log of all notifications.
-
-<br />
+Notifications can be received via various channels. For now, ClickHouse Cloud supports receiving notifications through email, ClickHouse Cloud UI, and Slack.  You can click on the bell icon in the top left menu to view current notifications, which opens a flyout. Clicking the button **View All** the bottom of the flyout will take you to a page that shows an activity log of all notifications.
 
 <Image img={notifications_1} size="md" alt="ClickHouse Cloud notifications flyout" border/>
 
-<br />
 
 <Image img={notifications_2} size="md" alt="ClickHouse Cloud notifications activity log" border/>
 
+
 ## Customizing Notifications {#customizing-notifications}
 
 For each notification, you can customize how you receive the notification. You can access the settings screen from the notifications flyout or from the second tab on the notifications activity log.
 
-To configure delivery for a specific notification, click on the pencil icon to modify the notification delivery channels.
+Cloud users can customize notifications delivered via the Cloud UI, and these customizations are reflected for each individual user. Cloud users can also customize notifications delivered to their own emails, but only users with admin permissions can customize notifications delivered to custom emails and notifications delivered to Slack channels.
 
-<br />
+To configure delivery for a specific notification, click on the pencil icon to modify the notification delivery channels.
 
 <Image img={notifications_3} size="md" alt="ClickHouse Cloud notifications settings screen" border/>
 
-<br />
-
 <Image img={notifications_4} size="md" alt="ClickHouse Cloud notification delivery settings" border/>
 
-<br />
-
 :::note
 Certain **required** notifications such as **Payment failed** are not configurable.
 :::
 
 ## Supported Notifications {#supported-notifications}
 
-Currently, we send out notifications related to billing (payment failure, usage exceeded ascertain threshold, etc.) as well as notifications related to scaling events (scaling completed, scaling blocked etc.). In future, we will add notifications for backups, ClickPipes, and other relevant categories.
+Currently, we send out notifications related to billing (payment failure, usage exceeded ascertain threshold, etc.) as well as notifications related to scaling events (scaling completed, scaling blocked etc.).

docs/cloud/reference/warehouses.md

@@ -140,6 +140,8 @@ settings distributed_ddl_task_timeout=0
 
 6. **In very rare cases, secondary services that are idled or stopped for a long time (days) without waking/starting up can cause performance degradation to other services in the same warehouse.** This issue will be resolved soon and is connected to mutations running in the background. If you think you are experiencing this issue, please contact ClickHouse [Support](https://clickhouse.com/support/program).
 
+7. **Currently there is a soft limit of 5 services per warehouse.** Contact the support team if you need more than 5 services in a single warehouse.
+
 
 ## Pricing {#pricing}
 

docs/whats-new/security-changelog.md

@@ -8,6 +8,18 @@ description: 'Security changelog detailing security related updates and changes'
 
 # Security Changelog
 
+## Fixed in ClickHouse v25.1.5.5, 2025-01-05 {#fixed-in-clickhouse-release-2025-01-05}
+
+### [CVE-2025-1385](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-5phv-x8x4-83x5) {#CVE-2025-1385}
+
+When the library bridge feature is enabled, the clickhouse-library-bridge exposes an HTTP API on localhost. This allows clickhouse-server to dynamically load a library from a specified path and execute it in an isolated process. Combined with the ClickHouse table engine functionality that permits file uploads to specific directories, a misconfigured server can be exploited by an attacker with privileges to access both table engines, allowing them to execute arbitrary code on the ClickHouse server.
+
+Fix has been pushed to the following open-source versions: v24.3.18.6, v24.8.14.27, v24.11.5.34, v24.12.5.65, v25.1.5.5
+
+ClickHouse Cloud is unaffected by this vulnerability.
+
+Credits: [Arseniy Dugin](https://github.com/ZerLes)
+
 ## Fixed in ClickHouse v24.5, 2024-08-01 {#fixed-in-clickhouse-release-2024-08-01}
 
 ### [CVE-2024-6873](https://github.com/ClickHouse/ClickHouse/security/advisories/GHSA-432f-r822-j66f) {#CVE-2024-6873}

plugins/floating-pages-exceptions.txt

@@ -9,3 +9,4 @@
 /docs/index.md
 integrations/language-clients/java/client-v1
 integrations/language-clients/java/jdbc-v1
+operations/userspace-page-cache

scripts/copy-clickhouse-repo-docs.sh

@@ -1,29 +1,32 @@
 #!/bin/bash
 
 function parse_args() {
+  force_pull=false
 
-  while getopts "hl:" opt; do
+  while getopts "hl:f" opt; do
     case "$opt" in
       h)
         # Display the usage information and exit when -h is provided
-        echo "Usage: $0 [-l path_to_local_clickhouse_repo]"
+        echo "Usage: $0 [-l path_to_local_clickhouse_repo] [-f]"
         echo ""
         echo "Options:"
         echo "  -l   Path to a local copy of the ClickHouse repository."
+        echo "  -f  Force pull from GitHub even in CI environment."
         echo "  -h   Display this help message."
         exit 0
         ;;
       l)
         local_path="$OPTARG"
         ;;
+      f)
+        force_pull=true
+        ;;
       \?)
         echo "Invalid option: -$OPTARG" >&2
         exit 1
         ;;
     esac
   done
-
-  echo "$local_path"
 }
 
 # Copy files/folders using rsync (or fallback to cp)
@@ -100,10 +103,14 @@ main() {
 
   if [[ -z "$local_path" ]]; then
 
-    if [[ "$CI" == "true" ]]; then
+    # Check if in CI environment and force_pull is not set
+    if [[ "$CI" == "true" && "$force_pull" == "false" ]]; then
       echo "CI environment detected, expecting /ClickHouse without having to pull the repo"
       copy_docs_locally "/ClickHouse"
     else
+      if [[ "$force_pull" == "true" && "$CI" == "true" ]]; then
+        echo "Force pull enabled, ignoring CI environment and pulling from GitHub"
+      fi
       git clone --depth 1 --branch master https://github.com/ClickHouse/ClickHouse
       # Copy docs from cloned repository
       copy_docs_locally "$(pwd)/ClickHouse"

sidebars.js

@@ -1110,6 +1110,7 @@ const sidebars = {
         "operations/optimizing-performance/sampling-query-profiler",
         "operations/query-cache",
         "operations/query-condition-cache",
+        "operations/userspace-page-cache",
         "operations/performance-test",
       ]
     }

vercel.json

@@ -3231,6 +3231,11 @@
       "destination": "/docs/sql-reference/data-types/float#bfloat16",
       "permanent": true
     },
+    {
+      "source": "/docs/introduction/distinctive-features",
+      "destination": "/docs/about-us/distinctive-features",
+      "permanent": true
+    },
     {
       "source": "/docs/en/:path*",
       "destination": "/docs/:path*"