Skip to content

Commit 20a03fb

Browse files
committed
update broken link
1 parent 0db4f7e commit 20a03fb

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/deployment-guides/replication-sharding-examples/03_2_shards_2_replicas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,8 @@ for separate local machines, virtual machines or cloud instances as well.
4646
Run the following commands to set up the directory structure for this example:
4747

4848
```bash
49-
mkdir clickhouse-cluster
50-
cd clickhouse-cluster
49+
mkdir cluster_2S_2R
50+
cd cluster_2S_2R
5151

5252
# Create clickhouse-keeper directories
5353
for i in {01..03}; do

docs/managing-data/core-concepts/shards.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ CREATE TABLE uk.uk_price_paid_simple_dist ON CLUSTER test_cluster
4949
ENGINE = Distributed('test_cluster', 'uk', 'uk_price_paid_simple', rand())
5050
```
5151

52-
The `ON CLUSTER` clause makes the DDL statement a [distributed DDL statement](/docs/sql-reference/distributed-ddl), instructing ClickHouse to create the table on all servers listed in the `test_cluster` [cluster definition](/architecture/replication/#configure-clickhouse-servers). Distributed DDL requires an additional [Keeper](https://clickhouse.com/clickhouse/keeper) component in the [cluster architecture](/docs/architecture/horizontal-scaling#architecture-diagram).
52+
The `ON CLUSTER` clause makes the DDL statement a [distributed DDL statement](/docs/sql-reference/distributed-ddl), instructing ClickHouse to create the table on all servers listed in the `test_cluster` [cluster definition](/architecture/replication/#configure-clickhouse-servers). Distributed DDL requires an additional [Keeper](https://clickhouse.com/clickhouse/keeper) component in the [cluster architecture](/architecture/horizontal-scaling).
5353

5454
For the [distributed engine parameters](/docs/engines/table-engines/special/distributed#distributed-parameters), we specify the cluster name (`test_cluster`), the database name (`uk`) for the sharded target table, the sharded target table's name (`uk_price_paid_simple`), and the **sharding key** for INSERT routing. In this example, we use the [rand](/sql-reference/functions/random-functions#rand) function to randomly assign rows to shards. However, any expression—even complex ones—can be used as a sharding key, depending on the use case. The next section illustrates how INSERT routing works.
5555

0 commit comments

Comments
 (0)