ClickHouse · mintlify · Jun 18, 2026
diff --git a/clickstack/features/dashboards/overview.mdx b/clickstack/features/dashboards/overview.mdx
@@ -37,7 +37,7 @@ For the examples below, we use the remote dataset available at [sql.clickhouse.c
 
 Select `Chart Explorer` from the left menu.
 
-<Image img="/images/use-cases/observability/hyperdx-visualization-1.png" alt="Chart Explorer" size="lg"/>
+<Image img="/images/use-cases/observability/clickstack-visualization-1.png" alt="Chart Explorer" size="lg"/>
 </Step>
 <Step>
 ### Create visualization {#create-visualization}
@@ -52,13 +52,17 @@ Select the `Line/Bar` visualization type from the top menu, followed by the `Tra
 - Group By: `ServiceName`  
 - Alias: `Average Time`
 
-<Image img="/images/use-cases/observability/hyperdx-visualization-2.png" alt="Simple visualization" size="lg"/>
+<Image img="/images/use-cases/observability/clickstack-visualization-2.png" alt="Simple visualization" size="lg"/>
 
 Note that you can filter events using either a SQL `WHERE` clause or Lucene syntax and set the time frame over which events should be visualized. Multiple series are also supported.
 
 For example, filter by the service `frontend` by adding the filter `ServiceName:"frontend"`. Add a second series for the count of events over time with the alias `Count` by clicking `Add Series`.
 
-<Image img="/images/use-cases/observability/hyperdx-visualization-3.png" alt="Simple visualization 2" size="lg"/>
+<Image img="/images/use-cases/observability/clickstack-visualization-3.png" alt="Simple visualization 2" size="lg"/>
+
+To build a series similar to an existing one, you can duplicate it instead of starting from scratch. Click the copy icon (`Duplicate series`) on a series row to insert a copy directly below. The copy keeps the source series' settings, such as the metric, column, and filter. You then change only the fields that differ (for example the aggregation) and give the copy its own alias. Duplicating is available wherever multiple series are supported. It is hidden for visualization types that allow only one series, such as `Number`, `Pie`, and `Heatmap`.
+
+<Image img="/images/use-cases/observability/clickstack-duplicate-series.png" alt="The Duplicate series copy icon and its tooltip on a chart series row" size="lg"/>
 
 <Note>
 Visualizations can be created from any data source — metrics, traces, or logs. ClickStack treats all of these as wide events. Any **numeric column** can be charted over time, and **string**, **date**, or **numeric** columns can be used for groupings.

diff --git a/get-started/migrate/postgres/appendix.mdx b/get-started/migrate/postgres/appendix.mdx
@@ -183,5 +183,5 @@ The following table shows the equivalent ClickHouse data types for Postgres.
 | `HSTORE` | [Map(K, V)](/reference/data-types/map), [Map](/reference/data-types/map)(K,[Variant](/reference/data-types/variant)) |
 | `UUID` | [UUID](/reference/data-types/uuid) |
 | `ARRAY<T>` | [ARRAY(T)](/reference/data-types/array) |
-| `JSON` | [String](/reference/data-types/string), [Variant](/reference/data-types/variant), [Nested](/reference/data-types/nested-data-structures#nestedname1-type1-name2-type2-), [Tuple](/reference/data-types/tuple) |
+| `JSON` | [String](/reference/data-types/string), [Variant](/reference/data-types/variant), [Nested](/reference/data-types/nested-data-structures), [Tuple](/reference/data-types/tuple) |
 | `JSONB` | [String](/reference/data-types/string) |
diff --git a/images/use-cases/observability/hyperdx-visualization-1.png b/images/use-cases/observability/hyperdx-visualization-1.png
diff --git a/images/use-cases/observability/hyperdx-visualization-2.png b/images/use-cases/observability/hyperdx-visualization-2.png
diff --git a/images/use-cases/observability/hyperdx-visualization-3.png b/images/use-cases/observability/hyperdx-visualization-3.png
diff --git a/integrations/clickpipes/home.mdx b/integrations/clickpipes/home.mdx
@@ -45,10 +45,10 @@ More connectors will get added to ClickPipes, you can find out more by [contacti
 
 The following tables list the static NAT IPs that ClickPipes uses to connect to your external services. Add the IPs for the ClickPipes region that serves your ClickHouse Cloud service to your IP allow list. In the case of object storage pipes you should also add the [ClickHouse cluster IPs](/products/cloud/guides/data-sources/cloud-endpoints-api) to your IP allow list.
 
-Services in the Google Cloud regions listed in the Google Cloud table below use those Google Cloud IPs only if the service was created on or after 27 May 2026. Services in those regions created before 27 May 2026 continue to use the default region IPs listed below.
+Services in the Google Cloud regions listed in the Google Cloud table below use those Google Cloud IPs only if the service did not contain pre-existing ClickPipes prior to June 15th, 2026. Services in those regions with pre-existing ClickPipes prior to June 15th, 2026 continue to use the default region IPs listed below.
 
 For other services, ClickPipes traffic will originate from a default region based on your service's location:
-- **eu-central-1**: For all EU regions not explicitly listed, plus Azure EU regions and Google Cloud EU services created before 27 May 2026.
+- **eu-central-1**: For all EU regions not explicitly listed, plus Azure EU regions and Google Cloud EU services with pre-existing ClickPipes prior to June 15th, 2026.
 - **eu-west-1**: For all services in AWS `eu-west-1` created on or after 20 Jan 2026 (services created before this date use `eu-central-1` IPs).
 - **us-east-1**: For all services in AWS `us-east-1`.
 - **ap-south-1**: For services in AWS `ap-south-1` created on or after 25 Jun 2025 (services created before this date use `us-east-2` IPs).
@@ -65,7 +65,7 @@ For other services, ClickPipes traffic will originate from a default region base
 - **il-central-1**: For services in AWS `il-central-1` created on or after 15 Apr 2026 (services created before this date use `us-east-2` IPs).
 - **sa-east-1**: For services in AWS `sa-east-1` created on or after 15 Apr 2026 (services created before this date use `us-east-2` IPs).
 - **us-west-2**: For services in AWS `us-west-2` created on or after 24 Jun 2025 (services created before this date use `us-east-2` IPs).
-- **us-east-2**: For all other regions that do not match a rule above, including Azure regions and Google Cloud services created before 27 May 2026.
+- **us-east-2**: For all other regions that do not match a rule above, including Azure regions and Google Cloud services with pre-existing ClickPipes prior to June 15th, 2026.
 
 ### AWS static NAT IPs {#aws-static-nat-ips}
 

diff --git a/integrations/clickpipes/mysql/parallel-initial-load.mdx b/integrations/clickpipes/mysql/parallel-initial-load.mdx
@@ -51,4 +51,3 @@ You can run **SHOW processlist** in MySQL to see the parallel snapshot in action
 ### Limitations {#limitations-parallel-mysql-snapshot}
 - The snapshot parameters can't be edited after pipe creation. If you want to change them, you will have to create a new ClickPipe.
 - When adding tables to an existing ClickPipe, you can't change the snapshot parameters. The ClickPipe will use the existing parameters for the new tables.
-- The partition key column shouldn't contain `NULL`s, as they're skipped by the partitioning logic.
diff --git a/integrations/clickpipes/postgres/parallel-initial-load.mdx b/integrations/clickpipes/postgres/parallel-initial-load.mdx
@@ -49,4 +49,3 @@ You can analyze **pg_stat_activity** to see the parallel snapshot in action. The
 
 - The snapshot parameters can't be edited after pipe creation. If you want to change them, you will have to create a new ClickPipe.
 - When adding tables to an existing ClickPipe, you can't change the snapshot parameters. The ClickPipe will use the existing parameters for the new tables.
-- The partition key column shouldn't contain `NULL`s, as they're skipped by the partitioning logic.
diff --git a/...rations/connectors/data-ingestion/etl-tools/dbt/features-and-configurations.mdx b/...rations/connectors/data-ingestion/etl-tools/dbt/features-and-configurations.mdx
@@ -47,6 +47,7 @@ your_profile_name:
       local_db_prefix: [<empty string>] # Database prefix of local tables on shards for distributed materializations. If empty, it uses the same database as the distributed table.
       allow_automatic_deduplication: [False] # Enable ClickHouse automatic deduplication for Replicated tables
       tcp_keepalive: [False] # Native client only, specify TCP keepalive configuration. Specify custom keepalive settings as [idle_time_sec, interval_sec, probes].
+      reuse_connections: [True] # Re-use the same connection across models. Set to `False` to close the connection at the end of each model — useful on multi-replica ClickHouse Cloud services where the load balancer routes by TCP connection.
       custom_settings: [{}] # A dictionary/mapping of custom ClickHouse settings for the connection - default is empty.
       database_engine: '' # Database engine to use when creating new ClickHouse schemas (databases).  If not set (the default), new databases will use the default ClickHouse database engine (usually Atomic).
       threads: [1] # Number of threads to use when running queries. Before setting it to a number higher than 1, make sure to read the [read-after-write consistency](#read-after-write-consistency) section.

diff --git a/resources/changelogs/cloud/2026.mdx b/resources/changelogs/cloud/2026.mdx
@@ -53,6 +53,8 @@ Fully managed Postgres on local NVMe storage is now in public beta, delivering 5
 
 Horizontal autoscaling automatically adjusts the number of replicas in a ClickHouse Cloud cluster based on the number of concurrent queries, scaling out when demand spikes and scaling in when load drops. Available in private preview for Enterprise and Scale tier customers on ClickHouse 26.2+. Contact support with your organization ID to enable.
 
+Note: For the intial GA launch, horizontal and vertical autoscaling are mutually exclusive. Horizontal autoscaling will only activate when vertical autoscaling is disabled (i.e., the service is set to a fixed size). The same applies to vertical autoscaling being enabled when the number of replicas is fixed. This behavior will become more flexible in future releases.
+
 ## May 25, 2026 {#2026-05-25}
 
 ### GA release of organization spend alerts {#spend-alerts-ga}

diff --git a/resources/changelogs/cloud/release-notes-index.mdx b/resources/changelogs/cloud/release-notes-index.mdx
@@ -14,6 +14,7 @@ keywords: ['changelog', 'release notes', 'updates', 'new features', 'cloud chang
 {/*AUTOGENERATED_START*/}
 | Page | Description |
 |-----|-----|
+| [v26.4 changelog for Cloud](/resources/changelogs/cloud/release-notes/26_04) | Changelog for v26.4 |
 | [v26.2 changelog for Cloud](/resources/changelogs/cloud/release-notes/26_02) | Changelog for v26.2 |
 | [v25.12 changelog for Cloud](/resources/changelogs/cloud/release-notes/25_12) | Changelog for v25.12 |
 | [v25.10 changelog for Cloud](/resources/changelogs/cloud/release-notes/25_10) | Changelog for v25.10 |
Original file line number	Diff line number	Diff line change
Expand Up		@@ -49,4 +49,3 @@ You can analyze pg_stat_activity to see the parallel snapshot in action. The

		- The snapshot parameters can't be edited after pipe creation. If you want to change them, you will have to create a new ClickPipe.
		- When adding tables to an existing ClickPipe, you can't change the snapshot parameters. The ClickPipe will use the existing parameters for the new tables.
		- The partition key column shouldn't contain `NULL`s, as they're skipped by the partitioning logic.