ClickHouse · Copilot · Jan 20, 2026 · Jan 26, 2026 · Jan 29, 2026 · Jan 30, 2026
diff --git a/docs/about-us/beta-and-experimental-features.md b/docs/about-us/beta-and-experimental-features.md
@@ -66,7 +66,6 @@ Please note: no additional experimental features are allowed to be enabled in Cl
 | [allow_statistics_optimize](/operations/settings/settings#allow_statistics_optimize) | `1` |
 | [use_statistics](/operations/settings/settings#use_statistics) | `1` |
 | [use_statistics_cache](/operations/settings/settings#use_statistics_cache) | `1` |
-| [enable_full_text_index](/operations/settings/settings#enable_full_text_index) | `1` |
 | [allow_experimental_delta_kernel_rs](/operations/settings/settings#allow_experimental_delta_kernel_rs) | `1` |
 | [allow_insert_into_iceberg](/operations/settings/settings#allow_insert_into_iceberg) | `0` |
 | [enable_join_runtime_filters](/operations/settings/settings#enable_join_runtime_filters) | `1` |
@@ -93,6 +92,9 @@ Please note: no additional experimental features are allowed to be enabled in Cl
 | [remote_fs_zero_copy_zookeeper_path](/operations/settings/merge-tree-settings#remote_fs_zero_copy_zookeeper_path) | `/clickhouse/zero_copy` |
 | [remove_rolled_back_parts_immediately](/operations/settings/merge-tree-settings#remove_rolled_back_parts_immediately) | `1` |
 | [shared_merge_tree_virtual_parts_discovery_batch](/operations/settings/merge-tree-settings#shared_merge_tree_virtual_parts_discovery_batch) | `1` |
+| [ast_fuzzer_runs](/operations/settings/settings#ast_fuzzer_runs) | `0` |
+| [ast_fuzzer_any_query](/operations/settings/settings#ast_fuzzer_any_query) | `0` |
+| [allow_fuzz_query_functions](/operations/settings/settings#allow_fuzz_query_functions) | `0` |
 | [allow_experimental_kafka_offsets_storage_in_keeper](/operations/settings/settings#allow_experimental_kafka_offsets_storage_in_keeper) | `0` |
 | [allow_experimental_delta_lake_writes](/operations/settings/settings#allow_experimental_delta_lake_writes) | `0` |
 | [automatic_parallel_replicas_mode](/operations/settings/settings#automatic_parallel_replicas_mode) | `0` |

diff --git a/docs/cloud/features/02_integrations.md b/docs/cloud/features/02_integrations.md
@@ -23,10 +23,33 @@ import Mongodbsvg from '@site/static/images/integrations/logos/mongodb.svg';
 import redpanda_logo from '@site/static/images/integrations/logos/logo_redpanda.png';
 import clickpipes_stack from '@site/static/images/integrations/data-ingestion/clickpipes/clickpipes_stack.png';
 import cp_custom_role from '@site/static/images/integrations/data-ingestion/clickpipes/cp_custom_role.png';
+import data_catalogs_ui from '@site/static/images/cloud/features/data-catalogs-ui.png';
 import Image from '@theme/IdealImage';
 
 ClickHouse Cloud allows you to connect the tools and services that you love.
 
+## Data Catalog Integrations (beta) {#data-catalog-integrations}
+
+ClickHouse Cloud can connect directly to your open table format data catalogs, giving you access to your data lake tables without duplicating data. By integrating, your catalog's tables will appear as queryable databases inside ClickHouse. Setup is available via SQL command ([DataLakeCatalog](/engines/database-engines/datalakecatalog)) and via the ClickHouse Cloud UI on the Data Sources tab.
+
+Using the UI:
+- Simplifies setup with a form using fields consistent with your Data Catalog objects 
+- One interface into active data catalog integrations
+- Tests connection and credentials when saving to validate connection was successful
+
+<Image img={data_catalogs_ui} size="md" alt="ClickHouse Cloud UI with data catalog integrations"/>
+
+| Name | Open Table Format Supported | Support | Version |
+|------|-----------------------------|---------|---------| 
+| AWS Glue Catalog | Iceberg | Cloud & Core | 25.10+ |
+| Lakekeeper | Iceberg  | Core | 26.1+ |
+| Microsoft OneLake | Iceberg | Cloud & Core | 25.12+ |
+| Nessie | Iceberg | Core | 26.1+ |
+| Polaris/Open Catalog | Iceberg | Core | 26.1+ |
+| REST catalog | Iceberg | Core | |
+| Unity Catalog | Iceberg (UniForm-enabled and managed), Delta | Cloud (Iceberg only) & Core | 25.10+ |
+
+
 ## Managed integration pipelines for ClickHouse Cloud {#clickpipes}
 
 ClickPipes is a managed integration platform that makes ingesting data from a diverse set of sources as simple as clicking a few buttons.

diff --git a/docs/cloud/guides/infrastructure/01_deployment_options/byoc/01_overview.md b/docs/cloud/guides/infrastructure/01_deployment_options/byoc/01_overview.md
@@ -25,7 +25,7 @@ BYOC is designed specifically for large-scale deployments, and requires customer
 **Supported Cloud Service Providers:**
 * AWS (GA)
 * GCP (Private Preview). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you're interested.
-* Azure (Roadmap). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you're interested.
+* Azure (Private Preview). Please join the waitlist [here](https://clickhouse.com/cloud/bring-your-own-cloud) if you're interested.
 
 **Supported Cloud Regions:**
 All **public regions** listed in our [supported regions](https://clickhouse.com/docs/cloud/reference/supported-regions) documentation are available for BYOC deployments. Private regions aren't currently supported.

diff --git a/...oard/02_migrate/01_migration_guides/08_other_methods/01_clickhouse-local-etl.md b/...oard/02_migrate/01_migration_guides/08_other_methods/01_clickhouse-local-etl.md
@@ -87,7 +87,7 @@ In order for the `remoteSecure` function to connect to your ClickHouse Cloud ser
 
   <AddARemoteSystem />
 
-## Example 1: Migrating from MySQL to ClickHouse Cloud with an Integration engine {#example-1-migrating-from-mysql-to-clickhouse-cloud-with-an-integration-engine}
+## Example: Migrating from MySQL to ClickHouse Cloud with an Integration engine {#example-1-migrating-from-mysql-to-clickhouse-cloud-with-an-integration-engine}
 
 We will use the [integration table engine](/engines/table-engines/integrations/mysql/) (created on-the-fly by the [mysql table function](/sql-reference/table-functions/mysql/)) for reading data from the source MySQL database and we will use the [remoteSecure table function](/sql-reference/table-functions/remote/)
 for writing the data into a destination table on your ClickHouse cloud service.
@@ -127,17 +127,3 @@ SELECT * FROM mysql('host:port', 'database', 'table', 'user', 'password');"
 No data is stored locally on the `clickhouse-local` host machine. Instead, the data is read from the source MySQL table
   and then immediately written to the destination table on the ClickHouse Cloud service.
 :::
-
-## Example 2: Migrating from MySQL to ClickHouse Cloud with the JDBC bridge {#example-2-migrating-from-mysql-to-clickhouse-cloud-with-the-jdbc-bridge}
-
-We will use the [JDBC integration table engine](/engines/table-engines/integrations/jdbc.md) (created on-the-fly by the [jdbc table function](/sql-reference/table-functions/jdbc.md)) together with the [ClickHouse JDBC Bridge](https://github.com/ClickHouse/clickhouse-jdbc-bridge) and the MySQL JDBC driver for reading data from the source MySQL database and we will use the [remoteSecure table function](/sql-reference/table-functions/remote.md)
-for writing the data into a destination table on your ClickHouse cloud service.
-
-<Image img={ch_local_04} size='lg' alt='Migrating Self-managed ClickHouse'  />
-
-### On the destination ClickHouse Cloud service: {#on-the-destination-clickhouse-cloud-service-1}
-
-#### Create the destination database: {#create-the-destination-database-1}
-  ```sql
-  CREATE DATABASE db
-  ```
diff --git a/docs/cloud/reference/01_changelog/01_changelog.md b/docs/cloud/reference/01_changelog/01_changelog.md
@@ -40,6 +40,9 @@ In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibil
   </a>
 :::
 
+## February 20, 2026 {#february-20-2026}
+- **ClickPipes:** Reverse private endpoints in an inactive state will now be automatically removed after a defined grace period. This ensures unused or misconfigured endpoints are not persisted indefinitely in the backend. See the automatic clean up [documentation](/integrations/clickpipes/aws-privatelink#automatic-cleanup) for more details.
+
 ## February 13, 2026 {#february-13-2026}
 - [BigQuery Connector](/integrations/clickpipes/bigquery/overview) is now in Private Preview. Read this [blogpost](https://clickhouse.com/blog/bigquery-clickpipe-private-preview) for more details and join the [waitlist](https://clickhouse.com/cloud/clickpipes/bigquery-connector) for access.
 - We are pleased to announce support for PCI deployments for Google Cloud. Regions supported: 

diff --git a/docs/cloud/reference/03_billing/05_payment-thresholds.md b/docs/cloud/reference/03_billing/05_payment-thresholds.md
@@ -7,14 +7,34 @@ keywords: ['billing', 'payment thresholds', 'automatic invoicing', 'invoice']
 doc_type: 'guide'
 ---
 
-# Payment thresholds
+import Image from '@theme/IdealImage';
+import billing_1 from '@site/static/images/cloud/reference/billing_payment_threshhold.png';
+import billing_2 from '@site/static/images/cloud/reference/billing_payment_threshhold_2.png';
 
-When your amount due in a billing period for ClickHouse Cloud reaches $10,000 USD or the equivalent value, your payment method will be automatically charged. A failed charge will result in the suspension or termination of your services after a grace period. 
+## Payment thresholds {#threshholds}
 
-:::note
-This payment threshold doesn't apply to customers who have a committed spend contract or other negotiated contractual agreement with ClickHouse.
+If you are a pay as you go customer and your amount due in a billing period for ClickHouse Cloud reaches $10,000 USD or the equivalent value, your payment method configured to your organization will be automatically charged. 
+
+:::tip
+This default payment threshold amount can be adjusted below $10,000.
+If you wish to do so, [contact support](support@clickhouse.com).
 :::
 
-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.
+A failed charge will result in the suspension of your services after a 14 day grace period.
+If you receive multiple invoices within a billing period, all are due upon receipt and must be paid to keep your ClickHouse Cloud organization [compliant](/manage/clickhouse-cloud-billing-compliance).
+
+If your automatic payment has a failed charge then it may be due to an issue with your configured credit card or that you have not set up an e-mandate on your credit card or your credit card is not compliant with the Reserve Bank of India (RBI) framework for processing of e-mandates for recurring online transactions.
+In case your credit cards are not RBI-complaint, you must add a new payment method that is RBI-compliant or continue making manual payments until you are able to set up the e-mandate on your card.
+
+In the example below, the Billing UI in cloud console is shown:
+
+<Image img={billing_1} size="sm" alt="Where to find billing in the UI"/>
+
+<Image img={billing_2} size="lg" alt="Bill"/>
+
+As you can see from the above example - there was a threshold invoice sent during the Feb 28-March 31 billing period and then there is another invoice sent during the same billing period for the remaining usage over $10,000.
+
+## Payment threshold notifications {#threshholds-notifications}
 
-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 support@clickhouse.com for more details.
+If your organization reaches 90% of the payment threshold and is on-track to exceed the payment threshold mid-period, the billing contact 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.
diff --git a/docs/integrations/data-ingestion/etl-tools/dbt/index.md b/docs/integrations/data-ingestion/etl-tools/dbt/index.md
@@ -32,7 +32,7 @@ dbt is compatible with ClickHouse through a [ClickHouse-supported adapter](https
 | [Features and Configurations](/integrations/dbt/features-and-configurations) | Description of the features and general configurations available |
 | [Materializations](/integrations/dbt/materializations) | Materializations available and their configurations |
 | [Guides](/integrations/dbt/guides) | Guides for using dbt with ClickHouse |
-| [Materialized Views](/integrations/dbt/materialization-materialized-view) | Specific documentation for the the materialized_view materialization |
+| [Materialization: materialized_view](/integrations/dbt/materialization-materialized-view) | Specific documentation for the materialized_view materialization |
 <!--AUTOGENERATED_END--> 
 
 ## Supported features {#supported-features}