Skip to content

Commit 1bc180b

Browse files
committed
Show blogs from 2023-01-01 (for content on JOINs), tweak keywords on some pages
1 parent 5ad30ca commit 1bc180b

23 files changed

+35
-25
lines changed

docs/best-practices/minimize_optimize_joins.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_position: 10
44
sidebar_label: 'Minimize and Optimize JOINs'
55
title: 'Minimize and optimize JOINs'
66
description: 'Page describing best practices for JOINs'
7-
keywords: ['JOIN', 'Join Algorithm']
7+
keywords: ['JOIN', 'Parallel Hash JOIN']
88
show_related_blogs: true
99
---
1010

docs/concepts/why-clickhouse-is-so-fast.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@ sidebar_label: 'Why is ClickHouse so Fast?'
44
description: 'It was designed to be fast. Query execution performance has always been a top priority during the development process, but other important characteristics like user-friendliness, scalability, and security were also considered so ClickHouse could become a real production system.'
55
title: 'Why is ClickHouse so fast?'
66
slug: /concepts/why-clickhouse-is-so-fast
7-
keywords: ['speed', 'fast']
7+
keywords: ['Architecture', 'VLDB', 'Performance']
8+
show_related_blogs: true
89
---
910

1011
# Why is ClickHouse so fast? {#why-clickhouse-is-so-fast}

docs/deployment-modes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ slug: /deployment-modes
33
sidebar_label: 'Deployment modes'
44
description: 'ClickHouse offers four deployment options that all use the same powerful database engine, just packaged differently to suit your specific needs.'
55
title: 'Deployment modes'
6-
keywords: ['Deployment Modes', 'chDB', 'clickhouse-local', 'ClickHouse Cloud']
6+
keywords: ['Deployment Modes', 'chDB']
77
show_related_blogs: true
88
---
99

docs/guides/developer/mutations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,10 @@
22
slug: /guides/developer/mutations
33
sidebar_label: 'Updating and Deleting Data'
44
sidebar_position: 1
5-
keywords: ['UPDATE', 'DELETE', 'mutation']
5+
keywords: ['UPDATE', 'DELETE']
66
title: 'Updating and deleting ClickHouse data'
77
description: 'Describes how to perform update and delete operations in ClickHouse'
8-
show_related_blogs: true
8+
show_related_blogs: false
99
---
1010

1111
# Updating and deleting ClickHouse data

docs/guides/inserting-data.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
22
title: 'Inserting ClickHouse data'
33
description: 'How to insert data into ClickHouse'
4-
keywords: ['insert', 'insert data', 'insert into table']
4+
keywords: ['INSERT', 'Batch Insert']
55
sidebar_label: 'Inserting ClickHouse data'
66
slug: /guides/inserting-data
7+
show_related_blogs: true
78
---
89

910
import postgres_inserts from '@site/static/images/guides/postgres-inserts.png';

docs/guides/writing-queries.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@ sidebar_label: 'Selecting data'
44
title: 'Selecting ClickHouse Data'
55
slug: /guides/writing-queries
66
description: 'Learn about Selecting ClickHouse Data'
7-
keywords: ['SELECT']
7+
keywords: ['SELECT', 'data formats']
8+
show_related_blogs: true
89
---
910

1011
ClickHouse is a SQL database, and you query your data by writing the same type of `SELECT` queries you are already familiar with. For example:

docs/integrations/data-ingestion/dbms/dynamodb/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ slug: /integrations/dynamodb
55
description: 'ClickPipes allows you to connect ClickHouse to DynamoDB.'
66
keywords: ['DynamoDB']
77
title: 'CDC from DynamoDB to ClickHouse'
8+
show_related_blogs: true
89
---
910

1011
import CloudNotSupportedBadge from '@theme/badges/CloudNotSupportedBadge';

docs/integrations/data-ingestion/dbms/mysql/index.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,9 @@ sidebar_label: 'MySQL'
33
sidebar_position: 10
44
slug: /integrations/connecting-to-mysql
55
description: 'The MySQL table engine allows you to connect ClickHouse to MySQL.'
6-
keywords: ['clickhouse', 'mysql', 'connect', 'integrate', 'table', 'engine']
6+
keywords: ['mysql']
77
title: 'Integrating MySQL with ClickHouse'
8+
show_related_blogs: true
89
---
910

1011
import CloudNotSupportedBadge from '@theme/badges/CloudNotSupportedBadge';

docs/integrations/migration/rockset.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
title: 'Migrating from Rockset'
33
slug: /migrations/rockset
44
description: 'Migrating from Rockset to ClickHouse'
5-
keywords: ['Rockset', 'migration']
5+
keywords: ['Rockset']
6+
show_related_blogs: true
67
---
78

89
# Migrating from Rockset

docs/migrations/bigquery/equivalent-concepts.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
title: 'BigQuery vs ClickHouse Cloud'
33
slug: /migrations/bigquery/biquery-vs-clickhouse-cloud
44
description: 'How BigQuery differs from ClickHouse Cloud'
5-
keywords: ['migrate', 'migration', 'migrating', 'data', 'etl', 'elt', 'BigQuery']
5+
keywords: ['BigQuery']
6+
show_related_blogs: true
67
---
78

89
import bigquery_1 from '@site/static/images/migrations/bigquery-1.png';

0 commit comments

Comments
 (0)