You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/managing-data/core-concepts/shards.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ Query processing works similarly to setups without replicas, with only a single
93
93
94
94
① A query targeting the distributed table is sent to corresponding ClickHouse server, either directly or via a load balancer.
95
95
96
-
② The Distributed table forwards the query to a one replica from each shard, where each ClickHouse server hosting the selected replica computes its local aggregation result in parallel.
96
+
② The Distributed table forwards the query to one replica from each shard, where each ClickHouse server hosting the selected replica computes its local aggregation result in parallel.
97
97
98
98
The rest works the [same](#select-forwarding) as in setups without replicas and is not shown in the diagram above. The ClickHouse server hosting the initially targeted distributed table collects all local results, merges them into the final global result, and returns it to the query sender.
0 commit comments