From 0b23e99fee7e37323a32bdcaddff76b3a340a837 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 21:31:25 +0000 Subject: [PATCH] docs: correct join_algorithm default (not auto) --- concepts/best-practices/minimize-optimize-joins.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/concepts/best-practices/minimize-optimize-joins.mdx b/concepts/best-practices/minimize-optimize-joins.mdx index 55e3a6777..06d776bbe 100644 --- a/concepts/best-practices/minimize-optimize-joins.mdx +++ b/concepts/best-practices/minimize-optimize-joins.mdx @@ -58,7 +58,7 @@ ClickHouse supports several JOIN algorithms that trade off between speed and mem Each algorithm has varying support for JOIN types. A full list of supported join types for each algorithm can be found [here](/concepts/features/operations/select/joining-tables#choosing-a-join-algorithm). -You can let ClickHouse choose the best algorithm by setting `join_algorithm = 'auto'` (the default), or explicitly control it based on your workload. If you need to select a join algorithm to optimize for performance or memory overhead, we recommend [this guide](/concepts/features/operations/select/joining-tables#choosing-a-join-algorithm). +You can let ClickHouse choose the best algorithm by setting `join_algorithm = 'auto'`, or explicitly control it based on your workload. The default value is `direct,parallel_hash,hash`, so ClickHouse uses a direct join when the right-hand side is a dictionary or key-value engine and otherwise falls back to parallel hash, then hash. If you need to select a join algorithm to optimize for performance or memory overhead, we recommend [this guide](/concepts/features/operations/select/joining-tables#choosing-a-join-algorithm). For optimal performance: