make sure articles have a heading after the prebody tags for formatti…

…ng reasons
Blargian · Jan 17, 2025 · 353c547 · 353c547
1 parent 6e9d63e
commit 353c547
Show file tree

Hide file tree

Showing 109 changed files with 184 additions and 192 deletions.
diff --git a/knowledgebase/Insert_select_settings_tuning.mdx b/knowledgebase/Insert_select_settings_tuning.mdx
@@ -1,22 +1,19 @@
 ---
-title: TOO MANY PARTS error during an `INSERT...SELECT`
+title: How do I solve TOO MANY PARTS error during an INSERT...SELECT?
 description: "Resolve the TOO_MANY_PARTS error in ClickHouse during an `INSERT...SELECT` by tuning expert-level settings for larger blocks and increasing partition thresholds."
 date: 2023-07-21
 tags: ['Settings', 'Errors and Exceptions']
 ---
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 
 When executing a `INSERT...SELECT` statement, I am getting too many parts (TOO_MANY_PARTS) error. 
 
 How can I solve this? 
 
-
-
 ## Answer
 
 Below are some of the settings to tune to avoid this error, this is expert level tuning of ClickHouse and these values should be set only after understanding the specifications of the ClickHouse cloud service or on-prem cluster where these will be used, so do not take these values as "one size fits all".

diff --git a/knowledgebase/ODBC-authentication-failed-error-using-PowerBI-CH-connector.mdx b/knowledgebase/ODBC-authentication-failed-error-using-PowerBI-CH-connector.mdx
@@ -8,14 +8,11 @@ keywords: ['ODBC', 'Power BI Connector', 'Authentication Failed']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-### Question
+## Question
 
 When trying to connect from PowerBI to ClickHouse using the connector, you receive a authentication error.
 
-
-
 This error usually looks like the following:
 
 ```
@@ -30,9 +27,7 @@ ClickHouse is installed.
 ```
 ![powerbi_error](./images/powerbi_odbc_authentication_error.png)
 
-
-
-### Answer
+## Answer
 
 Check the password being used to see if the password contains a tilde `~`.  
 

diff --git a/knowledgebase/about-quotas-and-query-complexity.mdx b/knowledgebase/about-quotas-and-query-complexity.mdx
@@ -8,9 +8,8 @@ description: 'Quotas and Query Complexity are powerful ways to limit and restric
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# About Quotas and Query complexity
+## About Quotas and Query complexity
 
 [Quotas](https://clickhouse.com/docs/en/operations/quotas) and [query complexity](https://clickhouse.com/docs/en/operations/settings/query-complexity) are powerful ways to limit and restrict what users can do in ClickHouse.
 

diff --git a/knowledgebase/add-column.mdx b/knowledgebase/add-column.mdx
@@ -8,7 +8,6 @@ keywords: ['Add Column']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 We'll be using clickhouse-local:
 

diff --git a/knowledgebase/alter-user-settings-exception.mdx b/knowledgebase/alter-user-settings-exception.mdx
@@ -8,9 +8,8 @@ keywords: ['Exception', 'User Settings']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# DB::Exception: Cannot update user `default` in users.xml because this storage is readonly. (ACCESS_STORAGE_READONLY)
+## DB::Exception: Cannot update user `default` in users.xml because this storage is readonly. (ACCESS_STORAGE_READONLY)
 
 When you try to alter a user's settings, you may encounter the above exception.
 

diff --git a/knowledgebase/are_materialized_views_inserted_asynchronously.mdx b/knowledgebase/are_materialized_views_inserted_asynchronously.mdx
@@ -8,9 +8,8 @@ keywords: ['Materialized View']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# Are Materialized Views inserted synchronously?
+## Are Materialized Views inserted synchronously?
 
 **Question:** When a source table has new rows inserted into it, those new rows are also sent to all of the materialized views of that source table. Are inserts into Materialized Views performed synchronously, meaning that once the insert is acknowledged successfully from the server to the client, it means that all Materialized Views have been fully updated and available for queries?
 

diff --git a/knowledgebase/async_vs_optimize_read_in_order.mdx b/knowledgebase/async_vs_optimize_read_in_order.mdx
@@ -8,9 +8,8 @@ keywords: ['Synchronous', 'Asynchronous', 'Data Reading']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# Synchronous data reading
+## Synchronous data reading
 
 The new setting allow_asynchronous_read_from_io_pool_for_merge_tree allows the number of reading threads (streams) to be higher than the number of threads in the rest of the query execution pipeline.
 

diff --git a/knowledgebase/aws-privatelink-setup-for-clickpipes.mdx b/knowledgebase/aws-privatelink-setup-for-clickpipes.mdx
@@ -8,9 +8,8 @@ keywords: ['AWS PrivateLink', 'Private RDS', 'ClickPipes']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# AWS PrivateLink setup to expose private RDS for ClickPipes
+## AWS PrivateLink setup to expose private RDS for ClickPipes
 
 Setup steps to expose a private RDS via AWS PrivateLink to ClickPipes.
 

diff --git a/knowledgebase/backing_up_a_specific_partition.mdx b/knowledgebase/backing_up_a_specific_partition.mdx
@@ -8,7 +8,6 @@ keywords: ['Backup', 'Partition']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 

diff --git a/knowledgebase/billing.mdx b/knowledgebase/billing.mdx
@@ -9,12 +9,9 @@ keywords: ['Billing', 'Cloud']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 import Content from '@site/docs/en/cloud/manage/billing.md';
 
-Overview of billing information.
-
-
+## Overview of billing information.
 
 <Content />
diff --git a/knowledgebase/calculate-pi-using-sql.mdx b/knowledgebase/calculate-pi-using-sql.mdx
@@ -8,9 +8,8 @@ keywords: ['Calculate Pi', 'SQL']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# It's Pi Day! Let's calculate pi using SQL
+## It's Pi Day! Let's calculate pi using SQL
 
 Happy Pi Day! We thought it would be fun to calculate pi using SQL queries in ClickHouse. Here is what we came up with so far...
 

diff --git a/knowledgebase/calculate_ratio_of_zero_sparse_serialization.mdx b/knowledgebase/calculate_ratio_of_zero_sparse_serialization.mdx
@@ -8,9 +8,8 @@ keywords: ['Empty/Zero Ratio', 'Calculate']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# How to calculate the ratio of empty/zero values in every column in a table
+## How to calculate the ratio of empty/zero values in every column in a table
 
 If a column is sparse (empty or contains mostly zeros), ClickHouse can encode it in a sparse format and automatically optimize calculations - the data does not require full decompression during queries. In fact, if you know how sparse a column is, you can define its ratio using the [`ratio_of_defaults_for_sparse_serialization` setting](https://clickhouse.com/docs/en/operations/settings/merge-tree-settings#ratio_of_defaults_for_sparse_serialization) to optimize serialization.
 

diff --git a/knowledgebase/cannot-append-data-to-parquet-format.mdx b/knowledgebase/cannot-append-data-to-parquet-format.mdx
@@ -8,9 +8,8 @@ keywords: ['Parquet', 'Cannot Append Data']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# Resolving "Cannot Append Data in Parquet Format" Error in ClickHouse
+## Resolving "Cannot Append Data in Parquet Format" Error in ClickHouse
 
 Are you getting the error "Cannot append data in format Parquet to file" error in ClickHouse?
 

diff --git a/knowledgebase/certificate_verify_failed_error.mdx b/knowledgebase/certificate_verify_failed_error.mdx
@@ -8,9 +8,8 @@ keywords: ['Error', 'SSL Certificate']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# Resolving SSL Certificate Verify Error in ClickHouse
+## Resolving SSL Certificate Verify Error in ClickHouse
 
 The error is typically reported as:
 

diff --git a/knowledgebase/change-billing-email.mdx b/knowledgebase/change-billing-email.mdx
@@ -8,9 +8,6 @@ keywords: ['Change Billing Contact', 'ClickHouse Cloud']
 
 {frontMatter.description}
 {/* truncate */}
----
-
-# How do I change my Billing Contact in ClickHouse Cloud?
 
 ## Question
 

diff --git a/knowledgebase/change-the-prompt-in-clickhouse-client.mdx b/knowledgebase/change-the-prompt-in-clickhouse-client.mdx
@@ -8,9 +8,8 @@ keywords: ['ClickHouse Client', 'Change Prompt']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# Change the prompt in `clickhouse client`
+## Change the prompt in `clickhouse client`
 
 Want to change your ClickHouse Client prompt? Read on.
 

diff --git a/knowledgebase/check-query-cache-in-use.mdx b/knowledgebase/check-query-cache-in-use.mdx
@@ -8,9 +8,8 @@ keywords: ['Query Cache']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# How can I check that query cache is being used in my query?
+## How can I check that query cache is being used in my query?
 
 See this example using [clickhouse client](https://clickhouse.com/docs/en/interfaces/cli) and ClickHouse Cloud service.
 

diff --git a/knowledgebase/check_query_processing_time_only.mdx b/knowledgebase/check_query_processing_time_only.mdx
@@ -8,7 +8,6 @@ keywords: ['Query Processing Time']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 

diff --git a/knowledgebase/check_users_roles.mdx b/knowledgebase/check_users_roles.mdx
@@ -8,13 +8,12 @@ keywords: ['User Roles']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-### Question
+## Question
 
 How to check users assigned to roles and vice versa?
 
-### Answer
+## Answer
 
 ```sql
 -- LOGGED IN AS default (admin privileges)

diff --git a/knowledgebase/clickhouse_cloud_api_usage.mdx b/knowledgebase/clickhouse_cloud_api_usage.mdx
@@ -8,9 +8,8 @@ keywords: ['cURL', 'Manage Cloud', 'ClickHouse API']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-# How to start, stop and resume a Cloud service using the ClickHouse API and cURL
+## How to start, stop and resume a Cloud service using the ClickHouse API and cURL
 
 ## Question
 

diff --git a/knowledgebase/columnar-database.mdx b/knowledgebase/columnar-database.mdx
@@ -8,7 +8,8 @@ keywords: ['Columnar Database']
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## Introduction
 
 A columnar database stores the data of each column independently. This allows reading data from disk only for those columns used in any given query. The cost is that operations that affect whole rows become proportionally more expensive. A columnar database is a synonym for a column-oriented database management system. ClickHouse is a typical example of such a system.
 

diff --git a/knowledgebase/common-rbac-queries.mdx b/knowledgebase/common-rbac-queries.mdx
@@ -8,7 +8,8 @@ keywords: ['RBAC', 'Queries']
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## Introduction
 
 The following are common queries to help grant specific permissions to users.
 

diff --git a/knowledgebase/compare_resultsets.mdx b/knowledgebase/compare_resultsets.mdx
@@ -8,14 +8,11 @@ keywords: ['Validate', 'Resultsets', 'Hash Functions']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 
 How can I validate that two queries return the same resultsets?
 
-
-
 ## Answer
 
 You can use the below approach:

diff --git a/knowledgebase/comparing-metrics-between-queries.mdx b/knowledgebase/comparing-metrics-between-queries.mdx
@@ -8,7 +8,8 @@ keywords: [compare queries, compare metrics, query performance]
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## Compare Metrics Between Two Queries
 
 To compare metrics between two queries, you must first obtain the `query_id` for both queries.
 

diff --git a/knowledgebase/configure-a-user-setting.mdx b/knowledgebase/configure-a-user-setting.mdx
@@ -8,7 +8,8 @@ keywords: ['SET', 'ALTER', 'User', 'Query', 'Session']
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## Introduction
 
 There are several ways to define a setting for a user in ClickHouse, depending on the use case and how long you want the setting to be configured. Let's look at a few scenarios...
 

diff --git a/knowledgebase/configure_cap_ipc_lock_and_cap_sys_nice_in_docker.mdx b/knowledgebase/configure_cap_ipc_lock_and_cap_sys_nice_in_docker.mdx
@@ -8,14 +8,11 @@ keywords: ['Docker', 'CAP_IPC_LOCK', 'CAP_SYS_NICE']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 
 When running ClickHouse in Docker, Docker is complaining about the lack of `CAP_IPC_LOCK` and `CAP_SYS_NICE` capabilities in the system. How can I resolve it?
 
-
-
 Here is what the no `CAP_SYS_NICE` or `CAP_SYS_NICE` capability log messages look like:
 
 ```bash

diff --git a/knowledgebase/connection_timeout_remote_remoteSecure.mdx b/knowledgebase/connection_timeout_remote_remoteSecure.mdx
@@ -10,7 +10,7 @@ keywords: ['Connection tries failed']
 {/* truncate */}
 ---
 
-# Code: 279. DB::NetException: All connection tries failed.
+## Code: 279. DB::NetException: All connection tries failed.
 
 **Problem**
 [`remote()` or `remoteSecure()`](https://clickhouse.com/docs/en/sql-reference/table-functions/remote/) table function allows the access of remote table from another ClickHouse node.

diff --git a/knowledgebase/dbms-naming.mdx b/knowledgebase/dbms-naming.mdx
@@ -1,14 +1,15 @@
 ---
 title: "What does \u201CClickHouse\u201D mean?"
-description: "It’s a combination of **Click**stream and Data ware**House**. It comes from the original use case at Yandex.Metrica, where ClickHouse was supposed to keep records of all clicks by people from all over the Internet, and it still does the job."
+description: "Curious what ClickHouse means? Take a look inside this knowledge base article to find out!"
 date: 2021-09-01
 tags: ['Concepts']
 keywords: ['ClickHouse Meaning']
 ---
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## ClickHouse Meaning Explained
 
 It’s a combination of "**Click**stream" and "Data ware**House**". It comes from the original use case at Yandex.Metrica, where ClickHouse was supposed to keep records of all clicks by people from all over the Internet, and it still does the job. You can read more about this use case on [ClickHouse history](https://clickhouse.com/docs/en/about-us/history) page.
 

diff --git a/knowledgebase/delete-old-data.mdx b/knowledgebase/delete-old-data.mdx
@@ -8,7 +8,8 @@ keywords: ['Delete Old Records']
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## The Short Answer Is "Yes"
 
 The short answer is "yes". ClickHouse has multiple mechanisms that allow freeing up disk space by removing old data. Each mechanism is aimed for different scenarios.
 

diff --git a/knowledgebase/dictionaries-consistent-state.mdx b/knowledgebase/dictionaries-consistent-state.mdx
@@ -8,7 +8,8 @@ keywords: ['Dictionaries']
 
 {frontMatter.description}
 {/* truncate */}
----
+
+## Dictionaries in ClickHouse
 
 Dictionaries created in ClickHouse Cloud may experience inconsistency during the initial creation phase. This means that you may not see any data in the dictionary right after creation. However, after several retries, the creation query may land on different replicas, and data will be visible.
 

diff --git a/knowledgebase/dictionary_using_strings.mdx b/knowledgebase/dictionary_using_strings.mdx
@@ -8,13 +8,12 @@ keywords: ['Dictionary', 'String Keys', 'String Values']
 
 {frontMatter.description}
 {/* truncate */}
----
 
-### Question
+## Question
 
 How to create a ClickHouse dictionary using string keys and string values from a MergeTree table source
 
-### Answer
+## Answer
 
 - Create the source table for the dictionary
 ```

diff --git a/knowledgebase/difference_between_official_builds_and_3rd_party.mdx b/knowledgebase/difference_between_official_builds_and_3rd_party.mdx
@@ -8,14 +8,11 @@ keywords: ['official builds', 'third-party builds']
 
 {frontMatter.description}
 {/* truncate */}
----
 
 ## Question
 
 I see other vendors providing their own builds of ClickHouse. What is the difference between official ClickHouse builds and these 3rd-party builds?
 
-
-
 ## Answer
 
 Here are some of the differences we have observed with other builds:
-Original file line number
+Diff line change
@@ Expand Up / @@ -8,7 +8,6 @@ keywords: ['Add Column'] @@
     {frontMatter.description}
     {/* truncate */}
-    ---
     We'll be using clickhouse-local:
@@ Expand Down @@