Merge branch 'master' into fix-mutations-again

.clang-tidy

@@ -62,6 +62,7 @@ Checks: '*,
 
     -google-build-using-namespace,
     -google-readability-braces-around-statements,
+    -google-readability-casting,
     -google-readability-function-size,
     -google-readability-namespace-comments,
     -google-readability-todo,

.github/workflows/master.yml

@@ -2911,7 +2911,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=0
           RUN_BY_HASH_TOTAL=4
@@ -2949,7 +2949,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=1
           RUN_BY_HASH_TOTAL=4
@@ -2987,7 +2987,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=2
           RUN_BY_HASH_TOTAL=4
@@ -3025,7 +3025,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=3
           RUN_BY_HASH_TOTAL=4

.github/workflows/pull_request.yml

@@ -3127,7 +3127,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=0
           RUN_BY_HASH_TOTAL=4
@@ -3165,7 +3165,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=1
           RUN_BY_HASH_TOTAL=4
@@ -3203,7 +3203,7 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=2
           RUN_BY_HASH_TOTAL=4
@@ -3241,7 +3241,159 @@ jobs:
           cat >> "$GITHUB_ENV" << 'EOF'
           TEMP_PATH=${{runner.temp}}/performance_comparison
           REPORTS_PATH=${{runner.temp}}/reports_dir
-          CHECK_NAME=Performance Comparison (actions)
+          CHECK_NAME=Performance Comparison
+          REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
+          RUN_BY_HASH_NUM=3
+          RUN_BY_HASH_TOTAL=4
+          EOF
+      - name: Download json reports
+        uses: actions/download-artifact@v2
+        with:
+          path: ${{ env.REPORTS_PATH }}
+      - name: Clear repository
+        run: |
+          sudo rm -fr "$GITHUB_WORKSPACE" && mkdir "$GITHUB_WORKSPACE"
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Performance Comparison
+        run: |
+          sudo rm -fr "$TEMP_PATH"
+          mkdir -p "$TEMP_PATH"
+          cp -r "$GITHUB_WORKSPACE" "$TEMP_PATH"
+          cd "$REPO_COPY/tests/ci"
+          python3 performance_comparison_check.py "$CHECK_NAME"
+      - name: Cleanup
+        if: always()
+        run: |
+          # shellcheck disable=SC2046
+          docker kill $(docker ps -q) ||:
+          # shellcheck disable=SC2046
+          docker rm -f $(docker ps -a -q) ||:
+          sudo rm -fr "$TEMP_PATH"
+  PerformanceComparisonAarch0:
+    needs: [BuilderDebAarch64]
+    runs-on: [self-hosted, func-tester-aarch64]
+    steps:
+      - name: Set envs
+        run: |
+          cat >> "$GITHUB_ENV" << 'EOF'
+          TEMP_PATH=${{runner.temp}}/performance_comparison
+          REPORTS_PATH=${{runner.temp}}/reports_dir
+          CHECK_NAME=Performance Comparison Aarch64
+          REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
+          RUN_BY_HASH_NUM=0
+          RUN_BY_HASH_TOTAL=4
+          EOF
+      - name: Download json reports
+        uses: actions/download-artifact@v2
+        with:
+          path: ${{ env.REPORTS_PATH }}
+      - name: Clear repository
+        run: |
+          sudo rm -fr "$GITHUB_WORKSPACE" && mkdir "$GITHUB_WORKSPACE"
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Performance Comparison
+        run: |
+          sudo rm -fr "$TEMP_PATH"
+          mkdir -p "$TEMP_PATH"
+          cp -r "$GITHUB_WORKSPACE" "$TEMP_PATH"
+          cd "$REPO_COPY/tests/ci"
+          python3 performance_comparison_check.py "$CHECK_NAME"
+      - name: Cleanup
+        if: always()
+        run: |
+          # shellcheck disable=SC2046
+          docker kill $(docker ps -q) ||:
+          # shellcheck disable=SC2046
+          docker rm -f $(docker ps -a -q) ||:
+          sudo rm -fr "$TEMP_PATH"
+  PerformanceComparisonAarch1:
+    needs: [BuilderDebAarch64]
+    runs-on: [self-hosted, func-tester-aarch64]
+    steps:
+      - name: Set envs
+        run: |
+          cat >> "$GITHUB_ENV" << 'EOF'
+          TEMP_PATH=${{runner.temp}}/performance_comparison
+          REPORTS_PATH=${{runner.temp}}/reports_dir
+          CHECK_NAME=Performance Comparison Aarch64
+          REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
+          RUN_BY_HASH_NUM=1
+          RUN_BY_HASH_TOTAL=4
+          EOF
+      - name: Download json reports
+        uses: actions/download-artifact@v2
+        with:
+          path: ${{ env.REPORTS_PATH }}
+      - name: Clear repository
+        run: |
+          sudo rm -fr "$GITHUB_WORKSPACE" && mkdir "$GITHUB_WORKSPACE"
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Performance Comparison
+        run: |
+          sudo rm -fr "$TEMP_PATH"
+          mkdir -p "$TEMP_PATH"
+          cp -r "$GITHUB_WORKSPACE" "$TEMP_PATH"
+          cd "$REPO_COPY/tests/ci"
+          python3 performance_comparison_check.py "$CHECK_NAME"
+      - name: Cleanup
+        if: always()
+        run: |
+          # shellcheck disable=SC2046
+          docker kill $(docker ps -q) ||:
+          # shellcheck disable=SC2046
+          docker rm -f $(docker ps -a -q) ||:
+          sudo rm -fr "$TEMP_PATH"
+  PerformanceComparisonAarch2:
+    needs: [BuilderDebAarch64]
+    runs-on: [self-hosted, func-tester-aarch64]
+    steps:
+      - name: Set envs
+        run: |
+          cat >> "$GITHUB_ENV" << 'EOF'
+          TEMP_PATH=${{runner.temp}}/performance_comparison
+          REPORTS_PATH=${{runner.temp}}/reports_dir
+          CHECK_NAME=Performance Comparison Aarch64
+          REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
+          RUN_BY_HASH_NUM=2
+          RUN_BY_HASH_TOTAL=4
+          EOF
+      - name: Download json reports
+        uses: actions/download-artifact@v2
+        with:
+          path: ${{ env.REPORTS_PATH }}
+      - name: Clear repository
+        run: |
+          sudo rm -fr "$GITHUB_WORKSPACE" && mkdir "$GITHUB_WORKSPACE"
+      - name: Check out repository code
+        uses: actions/checkout@v2
+      - name: Performance Comparison
+        run: |
+          sudo rm -fr "$TEMP_PATH"
+          mkdir -p "$TEMP_PATH"
+          cp -r "$GITHUB_WORKSPACE" "$TEMP_PATH"
+          cd "$REPO_COPY/tests/ci"
+          python3 performance_comparison_check.py "$CHECK_NAME"
+      - name: Cleanup
+        if: always()
+        run: |
+          # shellcheck disable=SC2046
+          docker kill $(docker ps -q) ||:
+          # shellcheck disable=SC2046
+          docker rm -f $(docker ps -a -q) ||:
+          sudo rm -fr "$TEMP_PATH"
+  PerformanceComparisonAarch3:
+    needs: [BuilderDebAarch64]
+    runs-on: [self-hosted, func-tester-aarch64]
+    steps:
+      - name: Set envs
+        run: |
+          cat >> "$GITHUB_ENV" << 'EOF'
+          TEMP_PATH=${{runner.temp}}/performance_comparison
+          REPORTS_PATH=${{runner.temp}}/reports_dir
+          CHECK_NAME=Performance Comparison Aarch64
           REPO_COPY=${{runner.temp}}/performance_comparison/ClickHouse
           RUN_BY_HASH_NUM=3
           RUN_BY_HASH_TOTAL=4
@@ -3333,6 +3485,10 @@ jobs:
       - PerformanceComparison1
       - PerformanceComparison2
       - PerformanceComparison3
+      - PerformanceComparisonAarch0
+      - PerformanceComparisonAarch1
+      - PerformanceComparisonAarch2
+      - PerformanceComparisonAarch3
       - UnitTestsAsan
       - UnitTestsTsan
       - UnitTestsMsan

base/base/ReplxxLineReader.cpp

@@ -45,14 +45,16 @@ std::string replxx_now_ms_str()
     time_t t = ms.count() / 1000;
     tm broken;
     if (!localtime_r(&t, &broken))
-    {
-        return std::string();
-    }
+        return {};
 
     static int const BUFF_SIZE(32);
     char str[BUFF_SIZE];
-    strftime(str, BUFF_SIZE, "%Y-%m-%d %H:%M:%S.", &broken);
-    snprintf(str + sizeof("YYYY-mm-dd HH:MM:SS"), 5, "%03d", static_cast<int>(ms.count() % 1000));
+    if (strftime(str, BUFF_SIZE, "%Y-%m-%d %H:%M:%S.", &broken) <= 0)
+        return {};
+
+    if (snprintf(str + sizeof("YYYY-mm-dd HH:MM:SS"), 5, "%03d", static_cast<int>(ms.count() % 1000)) <= 0)
+        return {};
+
     return str;
 }
 

base/base/wide_integer_impl.h

@@ -576,8 +576,8 @@ private:
         else if constexpr (Bits == 128 && sizeof(base_type) == 8)
         {
             using CompilerUInt128 = unsigned __int128;
-            CompilerUInt128 a = (CompilerUInt128(lhs.items[1]) << 64) + lhs.items[0];
-            CompilerUInt128 b = (CompilerUInt128(rhs.items[1]) << 64) + rhs.items[0];
+            CompilerUInt128 a = (CompilerUInt128(lhs.items[1]) << 64) + lhs.items[0]; // NOLINT(clang-analyzer-core.UndefinedBinaryOperatorResult)
+            CompilerUInt128 b = (CompilerUInt128(rhs.items[1]) << 64) + rhs.items[0]; // NOLINT(clang-analyzer-core.UndefinedBinaryOperatorResult)
             CompilerUInt128 c = a * b;
             integer<Bits, Signed> res;
             res.items[0] = c;
@@ -841,8 +841,8 @@ public:
         {
             using CompilerUInt128 = unsigned __int128;
 
-            CompilerUInt128 a = (CompilerUInt128(numerator.items[1]) << 64) + numerator.items[0];
-            CompilerUInt128 b = (CompilerUInt128(denominator.items[1]) << 64) + denominator.items[0];
+            CompilerUInt128 a = (CompilerUInt128(numerator.items[1]) << 64) + numerator.items[0]; // NOLINT(clang-analyzer-core.UndefinedBinaryOperatorResult)
+            CompilerUInt128 b = (CompilerUInt128(denominator.items[1]) << 64) + denominator.items[0]; // NOLINT(clang-analyzer-core.UndefinedBinaryOperatorResult)
             CompilerUInt128 c = a / b; // NOLINT
 
             integer<Bits, Signed> res;
@@ -1204,7 +1204,7 @@ constexpr integer<Bits, Signed>::operator T() const noexcept
 
     UnsignedT res{};
     for (unsigned i = 0; i < _impl::item_count && i < (sizeof(T) + sizeof(base_type) - 1) / sizeof(base_type); ++i)
-        res += UnsignedT(items[i]) << (sizeof(base_type) * 8 * i);
+        res += UnsignedT(items[i]) << (sizeof(base_type) * 8 * i); // NOLINT(clang-analyzer-core.UndefinedBinaryOperatorResult)
 
     return res;
 }

contrib/libxml2

@@ -1 +1 @@
-Subproject commit a075d256fd9ff15590b86d981b75a50ead124fca
+Subproject commit 7846b0a677f8d3ce72486125fa281e92ac9970e8

docker/packager/binary/Dockerfile

@@ -6,7 +6,7 @@ FROM ubuntu:20.04
 ARG apt_archive="http://archive.ubuntu.com"
 RUN sed -i "s|http://archive.ubuntu.com|$apt_archive|g" /etc/apt/sources.list
 
-ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=13
+ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=14
 
 RUN apt-get update \
     && apt-get install \

docker/packager/packager

@@ -319,25 +319,16 @@ if __name__ == "__main__":
     )
     parser.add_argument("--output-dir", type=dir_name, required=True)
     parser.add_argument("--build-type", choices=("debug", ""), default="")
+
     parser.add_argument(
         "--compiler",
         choices=(
-            "clang-11",
-            "clang-11-darwin",
-            "clang-11-darwin-aarch64",
-            "clang-11-aarch64",
-            "clang-12",
-            "clang-12-darwin",
-            "clang-12-darwin-aarch64",
-            "clang-12-aarch64",
-            "clang-13",
-            "clang-13-darwin",
-            "clang-13-darwin-aarch64",
-            "clang-13-aarch64",
-            "clang-13-ppc64le",
-            "clang-11-freebsd",
-            "clang-12-freebsd",
-            "clang-13-freebsd",
+            "clang-14",
+            "clang-14-darwin",
+            "clang-14-darwin-aarch64",
+            "clang-14-aarch64",
+            "clang-14-ppc64le",
+            "clang-14-freebsd",
             "gcc-11",
         ),
         default="clang-13",
@@ -348,6 +339,7 @@ if __name__ == "__main__":
         choices=("address", "thread", "memory", "undefined", ""),
         default="",
     )
+
     parser.add_argument("--split-binary", action="store_true")
     parser.add_argument("--clang-tidy", action="store_true")
     parser.add_argument("--cache", choices=("ccache", "distcc", ""), default="")

docker/test/base/Dockerfile

@@ -7,7 +7,7 @@ FROM clickhouse/test-util:$FROM_TAG
 ARG apt_archive="http://archive.ubuntu.com"
 RUN sed -i "s|http://archive.ubuntu.com|$apt_archive|g" /etc/apt/sources.list
 
-ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=13
+ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=14
 
 RUN apt-get update \
     && apt-get install ca-certificates lsb-release wget gnupg apt-transport-https \

docker/test/codebrowser/Dockerfile

@@ -8,14 +8,18 @@ FROM clickhouse/binary-builder:$FROM_TAG
 ARG apt_archive="http://archive.ubuntu.com"
 RUN sed -i "s|http://archive.ubuntu.com|$apt_archive|g" /etc/apt/sources.list
 
-RUN apt-get update && apt-get --yes --allow-unauthenticated install clang-13 libllvm13 libclang-13-dev libmlir-13-dev
+RUN apt-get update && apt-get --yes --allow-unauthenticated install clang-14 libllvm14 libclang-14-dev libmlir-14-dev
 
 # repo versions doesn't work correctly with C++17
 # also we push reports to s3, so we add index.html to subfolder urls
 # https://github.com/ClickHouse-Extras/woboq_codebrowser/commit/37e15eaf377b920acb0b48dbe82471be9203f76b
-RUN git clone https://github.com/ClickHouse-Extras/woboq_codebrowser
-
-RUN cd woboq_codebrowser && cmake . -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=clang\+\+-13 -DCMAKE_C_COMPILER=clang-13 && make -j
+# TODO: remove branch in a few weeks after merge, e.g. in May or June 2022
+RUN git clone https://github.com/ClickHouse-Extras/woboq_codebrowser --branch llvm-14 \
+  && cd woboq_codebrowser \
+  && cmake . -DCMAKE_BUILD_TYPE=Release -DCMAKE_CXX_COMPILER=clang\+\+-14 -DCMAKE_C_COMPILER=clang-14 \
+  && make -j \
+  && cd .. \
+  && rm -rf woboq_codebrowser
 
 ENV CODEGEN=/woboq_codebrowser/generator/codebrowser_generator
 ENV CODEINDEX=/woboq_codebrowser/indexgenerator/codebrowser_indexgenerator
@@ -28,7 +32,7 @@ ENV SHA=nosha
 ENV DATA="https://s3.amazonaws.com/clickhouse-test-reports/codebrowser/data"
 
 CMD mkdir -p $BUILD_DIRECTORY && cd $BUILD_DIRECTORY && \
-    cmake $SOURCE_DIRECTORY -DCMAKE_CXX_COMPILER=/usr/bin/clang\+\+-13 -DCMAKE_C_COMPILER=/usr/bin/clang-13 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DENABLE_EMBEDDED_COMPILER=0 -DENABLE_S3=0 && \
+    cmake $SOURCE_DIRECTORY -DCMAKE_CXX_COMPILER=/usr/bin/clang\+\+-14 -DCMAKE_C_COMPILER=/usr/bin/clang-14 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON -DENABLE_EMBEDDED_COMPILER=0 -DENABLE_S3=0 && \
     mkdir -p $HTML_RESULT_DIRECTORY && \
     $CODEGEN -b $BUILD_DIRECTORY -a -o $HTML_RESULT_DIRECTORY -p ClickHouse:$SOURCE_DIRECTORY:$SHA -d $DATA | ts '%Y-%m-%d %H:%M:%S' && \
     cp -r $STATIC_DATA $HTML_RESULT_DIRECTORY/ &&\

docker/test/fasttest/Dockerfile

@@ -7,7 +7,7 @@ FROM clickhouse/test-util:$FROM_TAG
 ARG apt_archive="http://archive.ubuntu.com"
 RUN sed -i "s|http://archive.ubuntu.com|$apt_archive|g" /etc/apt/sources.list
 
-ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=13
+ENV DEBIAN_FRONTEND=noninteractive LLVM_VERSION=14
 
 RUN apt-get update \
     && apt-get install ca-certificates lsb-release wget gnupg apt-transport-https \

docker/test/fuzzer/run-fuzzer.sh

@@ -12,7 +12,7 @@ stage=${stage:-}
 script_dir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
 echo "$script_dir"
 repo_dir=ch
-BINARY_TO_DOWNLOAD=${BINARY_TO_DOWNLOAD:="clang-13_debug_none_bundled_unsplitted_disable_False_binary"}
+BINARY_TO_DOWNLOAD=${BINARY_TO_DOWNLOAD:="clang-14_debug_none_bundled_unsplitted_disable_False_binary"}
 BINARY_URL_TO_DOWNLOAD=${BINARY_URL_TO_DOWNLOAD:="https://clickhouse-builds.s3.amazonaws.com/$PR_TO_TEST/$SHA_TO_TEST/clickhouse_build_check/$BINARY_TO_DOWNLOAD/clickhouse"}
 
 function clone

docker/test/keeper-jepsen/run.sh

@@ -2,7 +2,7 @@
 set -euo pipefail
 
 
-CLICKHOUSE_PACKAGE=${CLICKHOUSE_PACKAGE:="https://clickhouse-builds.s3.amazonaws.com/$PR_TO_TEST/$SHA_TO_TEST/clickhouse_build_check/clang-13_relwithdebuginfo_none_bundled_unsplitted_disable_False_binary/clickhouse"}
+CLICKHOUSE_PACKAGE=${CLICKHOUSE_PACKAGE:="https://clickhouse-builds.s3.amazonaws.com/$PR_TO_TEST/$SHA_TO_TEST/clickhouse_build_check/clang-14_relwithdebuginfo_none_bundled_unsplitted_disable_False_binary/clickhouse"}
 CLICKHOUSE_REPO_PATH=${CLICKHOUSE_REPO_PATH:=""}
 
 

docker/test/performance-comparison/compare.sh

@@ -207,6 +207,13 @@ function run_tests
         test_files=($(ls "$test_prefix"/*.xml))
     fi
 
+    # We can filter out certain tests
+    if [ -v CHPC_TEST_GREP_EXCLUDE ]; then
+        # filter tests array in bash https://stackoverflow.com/a/40375567
+        filtered_test_files=( $( for i in ${test_files[@]} ; do echo $i ; done | grep -v ${CHPC_TEST_GREP_EXCLUDE} ) )
+        test_files=("${filtered_test_files[@]}")
+    fi
+
     # We split perf tests into multiple checks to make them faster
     if [ -v CHPC_TEST_RUN_BY_HASH_TOTAL ]; then
         # filter tests array in bash https://stackoverflow.com/a/40375567

docker/test/stress/run.sh

@@ -338,6 +338,7 @@ then
                -e "Code: 1000, e.code() = 111, Connection refused" \
                -e "UNFINISHED" \
                -e "Renaming unexpected part" \
+               -e "PART_IS_TEMPORARILY_LOCKED" \
         /var/log/clickhouse-server/clickhouse-server.backward.clean.log | zgrep -Fa "<Error>" > /test_output/bc_check_error_messages.txt \
         && echo -e 'Backward compatibility check: Error message in clickhouse-server.log (see bc_check_error_messages.txt)\tFAIL' >> /test_output/test_results.tsv \
         || echo -e 'Backward compatibility check: No Error messages in clickhouse-server.log\tOK' >> /test_output/test_results.tsv

docs/_includes/cmake_in_clickhouse_header.md

@@ -6,8 +6,8 @@ Minimal ClickHouse build example:
 
 ```bash
 cmake .. \
-    -DCMAKE_C_COMPILER=$(which clang-13) \
-    -DCMAKE_CXX_COMPILER=$(which clang++-13) \
+    -DCMAKE_C_COMPILER=$(which clang-14) \
+    -DCMAKE_CXX_COMPILER=$(which clang++-14) \
     -DCMAKE_BUILD_TYPE=Debug \
     -DENABLE_UTILS=OFF \
     -DENABLE_TESTS=OFF

docs/en/development/build-cross-arm.md

@@ -10,7 +10,7 @@ This is intended for continuous integration checks that run on Linux servers.
 
 The cross-build for AARCH64 is based on the [Build instructions](../development/build.md), follow them first.
 
-## Install Clang-13
+## Install Clang-14 or newer
 
 Follow the instructions from https://apt.llvm.org/ for your Ubuntu or Debian setup or do
 ```
@@ -31,7 +31,7 @@ tar xJf gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz -C build-aarch64/cma
 ``` bash
 cd ClickHouse
 mkdir build-arm64
-CC=clang-13 CXX=clang++-13 cmake . -Bbuild-arm64 -DCMAKE_TOOLCHAIN_FILE=cmake/linux/toolchain-aarch64.cmake
+CC=clang-14 CXX=clang++-14 cmake . -Bbuild-arm64 -DCMAKE_TOOLCHAIN_FILE=cmake/linux/toolchain-aarch64.cmake
 ninja -C build-arm64
 ```
 

docs/en/development/build-cross-osx.md

@@ -10,14 +10,14 @@ This is intended for continuous integration checks that run on Linux servers. If
 
 The cross-build for Mac OS X is based on the [Build instructions](../development/build.md), follow them first.
 
-## Install Clang-13
+## Install Clang-14
 
 Follow the instructions from https://apt.llvm.org/ for your Ubuntu or Debian setup.
 For example the commands for Bionic are like:
 
 ``` bash
-sudo echo "deb [trusted=yes] http://apt.llvm.org/bionic/ llvm-toolchain-bionic-13 main" >> /etc/apt/sources.list
-sudo apt-get install clang-13
+sudo echo "deb [trusted=yes] http://apt.llvm.org/bionic/ llvm-toolchain-bionic-14 main" >> /etc/apt/sources.list
+sudo apt-get install clang-14
 ```
 
 ## Install Cross-Compilation Toolset {#install-cross-compilation-toolset}

docs/en/development/build-cross-riscv.md

@@ -23,7 +23,7 @@ sudo bash -c "$(wget -O - https://apt.llvm.org/llvm.sh)"
 ``` bash
 cd ClickHouse
 mkdir build-riscv64
-CC=clang-13 CXX=clang++-13 cmake . -Bbuild-riscv64 -G Ninja -DCMAKE_TOOLCHAIN_FILE=cmake/linux/toolchain-riscv64.cmake -DGLIBC_COMPATIBILITY=OFF -DENABLE_LDAP=OFF  -DOPENSSL_NO_ASM=ON -DENABLE_JEMALLOC=ON -DENABLE_PARQUET=OFF -DENABLE_ORC=OFF -DUSE_UNWIND=OFF -DENABLE_GRPC=OFF -DENABLE_HDFS=OFF -DENABLE_MYSQL=OFF
+CC=clang-14 CXX=clang++-14 cmake . -Bbuild-riscv64 -G Ninja -DCMAKE_TOOLCHAIN_FILE=cmake/linux/toolchain-riscv64.cmake -DGLIBC_COMPATIBILITY=OFF -DENABLE_LDAP=OFF  -DOPENSSL_NO_ASM=ON -DENABLE_JEMALLOC=ON -DENABLE_PARQUET=OFF -DENABLE_ORC=OFF -DUSE_UNWIND=OFF -DENABLE_GRPC=OFF -DENABLE_HDFS=OFF -DENABLE_MYSQL=OFF
 ninja -C build-riscv64
 ```
 

docs/en/development/build.md

@@ -77,7 +77,7 @@ The build requires the following components:
 -   Git (is used only to checkout the sources, it’s not needed for the build)
 -   CMake 3.14 or newer
 -   Ninja
--   C++ compiler: clang-13 or newer
+-   C++ compiler: clang-14 or newer
 -   Linker: lld
 
 If all the components are installed, you may build in the same way as the steps above.

docs/en/development/developer-instruction.md

@@ -155,7 +155,7 @@ While inside the `build` directory, configure your build by running CMake. Befor
     export CC=clang CXX=clang++
     cmake ..
 
-If you installed clang using the automatic installation script above, also specify the version of clang installed in the first command, e.g. `export CC=clang-13 CXX=clang++-13`. The clang version will be in the script output.
+If you installed clang using the automatic installation script above, also specify the version of clang installed in the first command, e.g. `export CC=clang-14 CXX=clang++-14`. The clang version will be in the script output.
 
 The `CC` variable specifies the compiler for C (short for C Compiler), and `CXX` variable instructs which C++ compiler is to be used for building.
 

docs/en/development/index.md

@@ -3,6 +3,6 @@ sidebar_label: Development
 sidebar_position: 58
 ---
 
-# ClickHouse Development {#clickhouse-development}
+# ClickHouse Development
 
 [Original article](https://clickhouse.com/docs/en/development/) <!--hide-->

docs/en/engines/database-engines/index.md

@@ -4,7 +4,7 @@ toc_priority: 27
 toc_title: Introduction
 ---
 
-# Database Engines {#database-engines}
+# Database Engines
 
 Database engines allow you to work with tables. By default, ClickHouse uses the [Atomic](../../engines/database-engines/atomic.md) database engine, which provides configurable [table engines](../../engines/table-engines/index.md) and an [SQL dialect](../../sql-reference/syntax.md).
 

docs/en/engines/database-engines/lazy.md

@@ -3,7 +3,7 @@ sidebar_label: Lazy
 sidebar_position: 20
 ---
 
-# Lazy {#lazy}
+# Lazy
 
 Keeps tables in RAM only `expiration_time_in_seconds` seconds after last access. Can be used only with \*Log tables.
 

docs/en/engines/database-engines/materialized-postgresql.md

@@ -3,7 +3,7 @@ sidebar_label: MaterializedPostgreSQL
 sidebar_position: 60
 ---
 
-# [experimental] MaterializedPostgreSQL {#materialize-postgresql}
+# [experimental] MaterializedPostgreSQL
 
 Creates a ClickHouse database with tables from PostgreSQL database. Firstly, database with engine `MaterializedPostgreSQL` creates a snapshot of PostgreSQL database and loads required tables. Required tables can include any subset of tables from any subset of schemas from specified database. Along with the snapshot database engine acquires LSN and once initial dump of tables is performed - it starts pulling updates from WAL. After database is created, newly added tables to PostgreSQL database are not automatically added to replication. They have to be added manually with `ATTACH TABLE db.table` query.
 

docs/en/engines/database-engines/postgresql.md

@@ -3,7 +3,7 @@ sidebar_position: 40
 sidebar_label: PostgreSQL
 ---
 
-# PostgreSQL {#postgresql}
+# PostgreSQL
 
 Allows to connect to databases on a remote [PostgreSQL](https://www.postgresql.org) server. Supports read and write operations (`SELECT` and `INSERT` queries) to exchange data between ClickHouse and PostgreSQL.
 

docs/en/engines/database-engines/replicated.md

@@ -3,7 +3,7 @@ sidebar_position: 30
 sidebar_label: Replicated
 ---
 
-# [experimental] Replicated {#replicated}
+# [experimental] Replicated
 
 The engine is based on the [Atomic](../../engines/database-engines/atomic.md) engine. It supports replication of metadata via DDL log being written to ZooKeeper and executed on all of the replicas for a given database.
 
@@ -20,7 +20,7 @@ One ClickHouse server can have multiple replicated databases running and updatin
 -   `shard_name` — Shard name. Database replicas are grouped into shards by `shard_name`.
 -   `replica_name` — Replica name. Replica names must be different for all replicas of the same shard.
 
-:::warning    
+:::warning
 For [ReplicatedMergeTree](../table-engines/mergetree-family/replication.md#table_engines-replication) tables if no arguments provided, then default arguments are used: `/clickhouse/tables/{uuid}/{shard}` and `{replica}`. These can be changed in the server settings [default_replica_path](../../operations/server-configuration-parameters/settings.md#default_replica_path) and [default_replica_name](../../operations/server-configuration-parameters/settings.md#default_replica_name). Macro `{uuid}` is unfolded to table's uuid, `{shard}` and `{replica}` are unfolded to values from server config, not from database engine arguments. But in the future, it will be possible to use `shard_name` and `replica_name` of Replicated database.
 :::
 

docs/en/engines/database-engines/sqlite.md

@@ -3,21 +3,21 @@ sidebar_position: 55
 sidebar_label: SQLite
 ---
 
-# SQLite {#sqlite}
+# SQLite
 
-Allows to connect to [SQLite](https://www.sqlite.org/index.html) database and perform `INSERT` and `SELECT` queries to exchange data between ClickHouse and SQLite. 
+Allows to connect to [SQLite](https://www.sqlite.org/index.html) database and perform `INSERT` and `SELECT` queries to exchange data between ClickHouse and SQLite.
 
 ## Creating a Database {#creating-a-database}
 
 ``` sql
-    CREATE DATABASE sqlite_database 
+    CREATE DATABASE sqlite_database
     ENGINE = SQLite('db_path')
 ```
 
 **Engine Parameters**
 
 -   `db_path` — Path to a file with SQLite database.
-    
+
 ## Data Types Support {#data_types-support}
 
 |  SQLite   | ClickHouse                                              |
@@ -44,7 +44,7 @@ SHOW TABLES FROM sqlite_db;
 ``` text
 ┌──name───┐
 │ table1  │
-│ table2  │  
+│ table2  │
 └─────────┘
 ```
 

docs/en/engines/table-engines/index.md

@@ -4,7 +4,7 @@ toc_priority: 26
 toc_title: Introduction
 ---
 
-# Table Engines {#table_engines}
+# Table Engines
 
 The table engine (type of table) determines:
 

docs/en/engines/table-engines/integrations/ExternalDistributed.md

@@ -3,7 +3,7 @@ sidebar_position: 12
 sidebar_label: ExternalDistributed
 ---
 
-# ExternalDistributed {#externaldistributed}
+# ExternalDistributed
 
 The `ExternalDistributed` engine allows to perform `SELECT` queries on data that is stored on a remote servers MySQL or PostgreSQL. Accepts [MySQL](../../../engines/table-engines/integrations/mysql.md) or [PostgreSQL](../../../engines/table-engines/integrations/postgresql.md) engines as an argument so sharding is possible.
 

docs/en/engines/table-engines/integrations/embedded-rocksdb.md

@@ -3,7 +3,7 @@ sidebar_position: 9
 sidebar_label: EmbeddedRocksDB
 ---
 
-# EmbeddedRocksDB Engine {#EmbeddedRocksDB-engine}
+# EmbeddedRocksDB Engine
 
 This engine allows integrating ClickHouse with [rocksdb](http://rocksdb.org/).
 

docs/en/engines/table-engines/integrations/hdfs.md

@@ -3,7 +3,7 @@ sidebar_position: 6
 sidebar_label: HDFS
 ---
 
-# HDFS {#table_engines-hdfs}
+# HDFS
 
 This engine provides integration with the [Apache Hadoop](https://en.wikipedia.org/wiki/Apache_Hadoop) ecosystem by allowing to manage data on [HDFS](https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html) via ClickHouse. This engine is similar to the [File](../../../engines/table-engines/special/file.md#table_engines-file) and [URL](../../../engines/table-engines/special/url.md#table_engines-url) engines, but provides Hadoop-specific features.
 
@@ -51,7 +51,7 @@ SELECT * FROM hdfs_engine_table LIMIT 2
 ## Implementation Details {#implementation-details}
 
 -   Reads and writes can be parallel.
--   [Zero-copy](../../../operations/storing-data.md#zero-copy) replication is supported.  
+-   [Zero-copy](../../../operations/storing-data.md#zero-copy) replication is supported.
 -   Not supported:
     -   `ALTER` and `SELECT...SAMPLE` operations.
     -   Indexes.
@@ -98,7 +98,7 @@ Table consists of all the files in both directories (all files should satisfy fo
 CREATE TABLE table_with_asterisk (name String, value UInt32) ENGINE = HDFS('hdfs://hdfs1:9000/{some,another}_dir/*', 'TSV')
 ```
 
-:::warning    
+:::warning
 If the listing of files contains number ranges with leading zeros, use the construction with braces for each digit separately or use `?`.
 :::
 

docs/en/engines/table-engines/integrations/hive.md

@@ -3,11 +3,11 @@ sidebar_position: 4
 sidebar_label: Hive
 ---
 
-# Hive {#hive}
+# Hive
 
 The Hive engine allows you to perform `SELECT` quries on HDFS Hive table. Currently it supports input formats as below:
 
-- Text: only supports simple scalar column types except `binary` 
+- Text: only supports simple scalar column types except `binary`
 
 - ORC: support simple scalar columns types except `char`; only support complex types like `array`
 
@@ -66,33 +66,33 @@ When ClickHouse is started up with local cache for remote filesystem enabled, us
 #### Create Table in Hive
 ``` text
 hive > CREATE TABLE `test`.`test_orc`(
-  `f_tinyint` tinyint, 
-  `f_smallint` smallint, 
-  `f_int` int, 
-  `f_integer` int, 
-  `f_bigint` bigint, 
-  `f_float` float, 
-  `f_double` double, 
-  `f_decimal` decimal(10,0), 
-  `f_timestamp` timestamp, 
-  `f_date` date, 
-  `f_string` string, 
-  `f_varchar` varchar(100), 
-  `f_bool` boolean, 
-  `f_binary` binary, 
-  `f_array_int` array<int>, 
-  `f_array_string` array<string>, 
-  `f_array_float` array<float>, 
-  `f_array_array_int` array<array<int>>, 
-  `f_array_array_string` array<array<string>>, 
+  `f_tinyint` tinyint,
+  `f_smallint` smallint,
+  `f_int` int,
+  `f_integer` int,
+  `f_bigint` bigint,
+  `f_float` float,
+  `f_double` double,
+  `f_decimal` decimal(10,0),
+  `f_timestamp` timestamp,
+  `f_date` date,
+  `f_string` string,
+  `f_varchar` varchar(100),
+  `f_bool` boolean,
+  `f_binary` binary,
+  `f_array_int` array<int>,
+  `f_array_string` array<string>,
+  `f_array_float` array<float>,
+  `f_array_array_int` array<array<int>>,
+  `f_array_array_string` array<array<string>>,
   `f_array_array_float` array<array<float>>)
-PARTITIONED BY ( 
+PARTITIONED BY (
   `day` string)
-ROW FORMAT SERDE 
-  'org.apache.hadoop.hive.ql.io.orc.OrcSerde' 
-STORED AS INPUTFORMAT 
-  'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat' 
-OUTPUTFORMAT 
+ROW FORMAT SERDE
+  'org.apache.hadoop.hive.ql.io.orc.OrcSerde'
+STORED AS INPUTFORMAT
+  'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat'
+OUTPUTFORMAT
   'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat'
 LOCATION
   'hdfs://testcluster/data/hive/test.db/test_orc'
@@ -178,7 +178,7 @@ f_array_array_float:  [[1.11,2.22],[3.33,4.44]]
 day:                  2021-09-18
 
 
-1 rows in set. Elapsed: 0.078 sec. 
+1 rows in set. Elapsed: 0.078 sec.
 ```
 
 ### Query Hive Table with Parquet Input Format
@@ -187,34 +187,34 @@ day:                  2021-09-18
 ``` text
 hive >
 CREATE TABLE `test`.`test_parquet`(
-  `f_tinyint` tinyint, 
-  `f_smallint` smallint, 
-  `f_int` int, 
-  `f_integer` int, 
-  `f_bigint` bigint, 
-  `f_float` float, 
-  `f_double` double, 
-  `f_decimal` decimal(10,0), 
-  `f_timestamp` timestamp, 
-  `f_date` date, 
-  `f_string` string, 
-  `f_varchar` varchar(100), 
-  `f_char` char(100), 
-  `f_bool` boolean, 
-  `f_binary` binary, 
-  `f_array_int` array<int>, 
-  `f_array_string` array<string>, 
-  `f_array_float` array<float>, 
-  `f_array_array_int` array<array<int>>, 
-  `f_array_array_string` array<array<string>>, 
+  `f_tinyint` tinyint,
+  `f_smallint` smallint,
+  `f_int` int,
+  `f_integer` int,
+  `f_bigint` bigint,
+  `f_float` float,
+  `f_double` double,
+  `f_decimal` decimal(10,0),
+  `f_timestamp` timestamp,
+  `f_date` date,
+  `f_string` string,
+  `f_varchar` varchar(100),
+  `f_char` char(100),
+  `f_bool` boolean,
+  `f_binary` binary,
+  `f_array_int` array<int>,
+  `f_array_string` array<string>,
+  `f_array_float` array<float>,
+  `f_array_array_int` array<array<int>>,
+  `f_array_array_string` array<array<string>>,
   `f_array_array_float` array<array<float>>)
-PARTITIONED BY ( 
+PARTITIONED BY (
   `day` string)
-ROW FORMAT SERDE 
-  'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe' 
-STORED AS INPUTFORMAT 
-  'org.apache.hadoop.hive.ql.io.parquet.MapredParquetInputFormat' 
-OUTPUTFORMAT 
+ROW FORMAT SERDE
+  'org.apache.hadoop.hive.ql.io.parquet.serde.ParquetHiveSerDe'
+STORED AS INPUTFORMAT
+  'org.apache.hadoop.hive.ql.io.parquet.MapredParquetInputFormat'
+OUTPUTFORMAT
   'org.apache.hadoop.hive.ql.io.parquet.MapredParquetOutputFormat'
 LOCATION
   'hdfs://testcluster/data/hive/test.db/test_parquet'
@@ -299,7 +299,7 @@ f_array_array_string: [['a','b'],['c','d']]
 f_array_array_float:  [[1.11,2.22],[3.33,4.44]]
 day:                  2021-09-18
 
-1 rows in set. Elapsed: 0.357 sec. 
+1 rows in set. Elapsed: 0.357 sec.
 ```
 
 ### Query Hive Table with Text Input Format
@@ -307,34 +307,34 @@ day:                  2021-09-18
 ``` text
 hive >
 CREATE TABLE `test`.`test_text`(
-  `f_tinyint` tinyint, 
-  `f_smallint` smallint, 
-  `f_int` int, 
-  `f_integer` int, 
-  `f_bigint` bigint, 
-  `f_float` float, 
-  `f_double` double, 
-  `f_decimal` decimal(10,0), 
-  `f_timestamp` timestamp, 
-  `f_date` date, 
-  `f_string` string, 
-  `f_varchar` varchar(100), 
-  `f_char` char(100), 
-  `f_bool` boolean, 
-  `f_binary` binary, 
-  `f_array_int` array<int>, 
-  `f_array_string` array<string>, 
-  `f_array_float` array<float>, 
-  `f_array_array_int` array<array<int>>, 
-  `f_array_array_string` array<array<string>>, 
+  `f_tinyint` tinyint,
+  `f_smallint` smallint,
+  `f_int` int,
+  `f_integer` int,
+  `f_bigint` bigint,
+  `f_float` float,
+  `f_double` double,
+  `f_decimal` decimal(10,0),
+  `f_timestamp` timestamp,
+  `f_date` date,
+  `f_string` string,
+  `f_varchar` varchar(100),
+  `f_char` char(100),
+  `f_bool` boolean,
+  `f_binary` binary,
+  `f_array_int` array<int>,
+  `f_array_string` array<string>,
+  `f_array_float` array<float>,
+  `f_array_array_int` array<array<int>>,
+  `f_array_array_string` array<array<string>>,
   `f_array_array_float` array<array<float>>)
-PARTITIONED BY ( 
+PARTITIONED BY (
   `day` string)
-ROW FORMAT SERDE 
-  'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe' 
-STORED AS INPUTFORMAT 
-  'org.apache.hadoop.mapred.TextInputFormat' 
-OUTPUTFORMAT 
+ROW FORMAT SERDE
+  'org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe'
+STORED AS INPUTFORMAT
+  'org.apache.hadoop.mapred.TextInputFormat'
+OUTPUTFORMAT
   'org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat'
 LOCATION
   'hdfs://testcluster/data/hive/test.db/test_text'
@@ -374,7 +374,7 @@ CREATE TABLE test.test_text
     `day` String
 )
 ENGINE = Hive('thrift://localhost:9083', 'test', 'test_text')
-PARTITION BY day 
+PARTITION BY day
 ```
 
 ``` sql

docs/en/engines/table-engines/integrations/index.md

@@ -3,7 +3,7 @@ sidebar_position: 40
 sidebar_label:  Integrations
 ---
 
-# Table Engines for Integrations {#table-engines-for-integrations}
+# Table Engines for Integrations
 
 ClickHouse provides various means for integrating with external systems, including table engines. Like with all other table engines, the configuration is done using `CREATE TABLE` or `ALTER TABLE` queries. Then from a user perspective, the configured integration looks like a normal table, but queries to it are proxied to the external system. This transparent querying is one of the key advantages of this approach over alternative integration methods, like external dictionaries or table functions, which require to use custom query methods on each use.
 

docs/en/engines/table-engines/integrations/jdbc.md

@@ -3,7 +3,7 @@ sidebar_position: 3
 sidebar_label: JDBC
 ---
 
-# JDBC {#table-engine-jdbc}
+# JDBC
 
 Allows ClickHouse to connect to external databases via [JDBC](https://en.wikipedia.org/wiki/Java_Database_Connectivity).
 

docs/en/engines/table-engines/integrations/kafka.md

@@ -3,7 +3,7 @@ sidebar_position: 8
 sidebar_label: Kafka
 ---
 
-# Kafka {#kafka}
+# Kafka
 
 This engine works with [Apache Kafka](http://kafka.apache.org/).
 
@@ -87,7 +87,7 @@ Examples:
 
 <summary>Deprecated Method for Creating a Table</summary>
 
-:::warning    
+:::warning
 Do not use this method in new projects. If possible, switch old projects to the method described above.
 :::
 

docs/en/engines/table-engines/integrations/materialized-postgresql.md

@@ -3,7 +3,7 @@ sidebar_position: 12
 sidebar_label: MaterializedPostgreSQL
 ---
 
-# MaterializedPostgreSQL {#materialize-postgresql}
+# MaterializedPostgreSQL
 
 Creates ClickHouse table with an initial data dump of PostgreSQL table and starts replication process, i.e. executes background job to apply new changes as they happen on PostgreSQL table in the remote PostgreSQL database.
 
@@ -52,7 +52,7 @@ PRIMARY KEY key;
 SELECT key, value, _version FROM postgresql_db.postgresql_replica;
 ```
 
-:::warning    
+:::warning
 Replication of [**TOAST**](https://www.postgresql.org/docs/9.5/storage-toast.html) values is not supported. The default value for the data type will be used.
 :::
 

docs/en/engines/table-engines/integrations/mongodb.md

@@ -3,7 +3,7 @@ sidebar_position: 5
 sidebar_label: MongoDB
 ---
 
-# MongoDB {#mongodb}
+# MongoDB
 
 MongoDB engine is read-only table engine which allows to read data (`SELECT` queries) from remote MongoDB collection. Engine supports only non-nested data types. `INSERT` queries are not supported.
 

docs/en/engines/table-engines/integrations/mysql.md

@@ -3,7 +3,7 @@ sidebar_position: 4
 sidebar_label: MySQL
 ---
 
-# MySQL {#mysql}
+# MySQL
 
 The MySQL engine allows you to perform `SELECT` and `INSERT` queries on data that is stored on a remote MySQL server.
 

docs/en/engines/table-engines/integrations/odbc.md

@@ -3,7 +3,7 @@ sidebar_position: 2
 sidebar_label: ODBC
 ---
 
-# ODBC {#table-engine-odbc}
+# ODBC
 
 Allows ClickHouse to connect to external databases via [ODBC](https://en.wikipedia.org/wiki/Open_Database_Connectivity).
 

docs/en/engines/table-engines/integrations/postgresql.md

@@ -3,7 +3,7 @@ sidebar_position: 11
 sidebar_label: PostgreSQL
 ---
 
-# PostgreSQL {#postgresql}
+# PostgreSQL
 
 The PostgreSQL engine allows to perform `SELECT` and `INSERT` queries on data that is stored on a remote PostgreSQL server.
 

docs/en/engines/table-engines/integrations/rabbitmq.md

@@ -3,7 +3,7 @@ sidebar_position: 10
 sidebar_label: RabbitMQ
 ---
 
-# RabbitMQ Engine {#rabbitmq-engine}
+# RabbitMQ Engine
 
 This engine allows integrating ClickHouse with [RabbitMQ](https://www.rabbitmq.com).
 

docs/en/engines/table-engines/integrations/s3.md

@@ -3,7 +3,7 @@ sidebar_position: 7
 sidebar_label: S3
 ---
 
-# S3 Table Engine {#table-engine-s3}
+# S3 Table Engine
 
 This engine provides integration with [Amazon S3](https://aws.amazon.com/s3/) ecosystem. This engine is similar to the [HDFS](../../../engines/table-engines/special/file.md#table_engines-hdfs) engine, but provides S3-specific features.
 
@@ -25,7 +25,7 @@ CREATE TABLE s3_engine_table (name String, value UInt32)
 **Example**
 
 ``` sql
-CREATE TABLE s3_engine_table (name String, value UInt32) 
+CREATE TABLE s3_engine_table (name String, value UInt32)
     ENGINE=S3('https://clickhouse-public-datasets.s3.amazonaws.com/my-test-bucket-768/test-data.csv.gz', 'CSV', 'gzip')
     SETTINGS input_format_with_names_use_header = 0;
 
@@ -50,7 +50,7 @@ For more information about virtual columns see [here](../../../engines/table-eng
 ## Implementation Details {#implementation-details}
 
 -   Reads and writes can be parallel
--   [Zero-copy](../../../operations/storing-data.md#zero-copy) replication is supported.  
+-   [Zero-copy](../../../operations/storing-data.md#zero-copy) replication is supported.
 -   Not supported:
     -   `ALTER` and `SELECT...SAMPLE` operations.
     -   Indexes.
@@ -66,7 +66,7 @@ For more information about virtual columns see [here](../../../engines/table-eng
 
 Constructions with `{}` are similar to the [remote](../../../sql-reference/table-functions/remote.md) table function.
 
-:::warning    
+:::warning
 If the listing of files contains number ranges with leading zeros, use the construction with braces for each digit separately or use `?`.
 :::
 

docs/en/engines/table-engines/integrations/sqlite.md

@@ -3,16 +3,16 @@ sidebar_position: 7
 sidebar_label: SQLite
 ---
 
-# SQLite {#sqlite}
+# SQLite
 
 The engine allows to import and export data to SQLite and supports queries to SQLite tables directly from ClickHouse.
 
 ## Creating a Table {#creating-a-table}
 
 ``` sql
-    CREATE TABLE [IF NOT EXISTS] [db.]table_name 
+    CREATE TABLE [IF NOT EXISTS] [db.]table_name
     (
-        name1 [type1], 
+        name1 [type1],
         name2 [type2], ...
     ) ENGINE = SQLite('db_path', 'table')
 ```
@@ -32,10 +32,10 @@ SHOW CREATE TABLE sqlite_db.table2;
 
 ``` text
 CREATE TABLE SQLite.table2
-( 
-    `col1` Nullable(Int32), 
+(
+    `col1` Nullable(Int32),
     `col2` Nullable(String)
-) 
+)
 ENGINE = SQLite('sqlite.db','table2');
 ```
 

docs/en/engines/table-engines/log-family/index.md

@@ -3,7 +3,7 @@ sidebar_position: 20
 sidebar_label:  Log Family
 ---
 
-# Log Engine Family {#log-engine-family}
+# Log Engine Family
 
 These engines were developed for scenarios when you need to quickly write many small tables (up to about 1 million rows) and read them later as a whole.
 

docs/en/engines/table-engines/log-family/log.md

@@ -3,7 +3,7 @@ toc_priority: 33
 toc_title: Log
 ---
 
-# Log {#log}
+# Log
 
 The engine belongs to the family of `Log` engines. See the common properties of `Log` engines and their differences in the [Log Engine Family](../../../engines/table-engines/log-family/index.md) article.
 

docs/en/engines/table-engines/log-family/stripelog.md

@@ -3,7 +3,7 @@ toc_priority: 32
 toc_title: StripeLog
 ---
 
-# Stripelog {#stripelog}
+# Stripelog
 
 This engine belongs to the family of log engines. See the common properties of log engines and their differences in the [Log Engine Family](../../../engines/table-engines/log-family/index.md) article.
 

docs/en/engines/table-engines/log-family/tinylog.md

@@ -3,7 +3,7 @@ toc_priority: 34
 toc_title: TinyLog
 ---
 
-# TinyLog {#tinylog}
+# TinyLog
 
 The engine belongs to the log engine family. See [Log Engine Family](../../../engines/table-engines/log-family/index.md) for common properties of log engines and their differences.
 

docs/en/engines/table-engines/mergetree-family/aggregatingmergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 60
 sidebar_label:  AggregatingMergeTree
 ---
 
-# AggregatingMergeTree {#aggregatingmergetree}
+# AggregatingMergeTree
 
 The engine inherits from [MergeTree](../../../engines/table-engines/mergetree-family/mergetree.md#table_engines-mergetree), altering the logic for data parts merging. ClickHouse replaces all rows with the same primary key (or more accurately, with the same [sorting key](../../../engines/table-engines/mergetree-family/mergetree.md)) with a single row (within a one data part) that stores a combination of states of aggregate functions.
 

docs/en/engines/table-engines/mergetree-family/collapsingmergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 70
 sidebar_label: CollapsingMergeTree
 ---
 
-# CollapsingMergeTree {#table_engine-collapsingmergetree}
+# CollapsingMergeTree
 
 The engine inherits from [MergeTree](../../../engines/table-engines/mergetree-family/mergetree.md) and adds the logic of rows collapsing to data parts merge algorithm.
 
@@ -42,7 +42,7 @@ When creating a `CollapsingMergeTree` table, the same [query clauses](../../../e
 
 <summary>Deprecated Method for Creating a Table</summary>
 
-:::warning    
+:::warning
 Do not use this method in new projects and, if possible, switch old projects to the method described above.
 :::
 

docs/en/engines/table-engines/mergetree-family/custom-partitioning-key.md

@@ -3,10 +3,10 @@ sidebar_position: 30
 sidebar_label: Custom Partitioning Key
 ---
 
-# Custom Partitioning Key {#custom-partitioning-key}
+# Custom Partitioning Key
 
-:::warning   
-In most cases you do not need a partition key, and in most other cases you do not need a partition key more granular than by months. Partitioning does not speed up queries (in contrast to the ORDER BY expression). 
+:::warning
+In most cases you do not need a partition key, and in most other cases you do not need a partition key more granular than by months. Partitioning does not speed up queries (in contrast to the ORDER BY expression).
 
 You should never use too granular of partitioning. Don't partition your data by client identifiers or names. Instead, make a client identifier or name the first column in the ORDER BY expression.
 :::
@@ -43,7 +43,7 @@ By default, the floating-point partition key is not supported. To use it enable
 
 When inserting new data to a table, this data is stored as a separate part (chunk) sorted by the primary key. In 10-15 minutes after inserting, the parts of the same partition are merged into the entire part.
 
-:::info    
+:::info
 A merge only works for data parts that have the same value for the partitioning expression. This means **you shouldn’t make overly granular partitions** (more than about a thousand partitions). Otherwise, the `SELECT` query performs poorly because of an unreasonably large number of files in the file system and open file descriptors.
 :::
 

docs/en/engines/table-engines/mergetree-family/graphitemergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 90
 sidebar_label:  GraphiteMergeTree
 ---
 
-# GraphiteMergeTree {#graphitemergetree}
+# GraphiteMergeTree
 
 This engine is designed for thinning and aggregating/averaging (rollup) [Graphite](http://graphite.readthedocs.io/en/latest/index.html) data. It may be helpful to developers who want to use ClickHouse as a data store for Graphite.
 
@@ -54,7 +54,7 @@ When creating a `GraphiteMergeTree` table, the same [clauses](../../../engines/t
 
 <summary>Deprecated Method for Creating a Table</summary>
 
-:::warning    
+:::warning
 Do not use this method in new projects and, if possible, switch old projects to the method described above.
 :::
 
@@ -120,7 +120,7 @@ default
     ...
 ```
 
-:::warning    
+:::warning
 Patterns must be strictly ordered:
 
 1. Patterns without `function` or `retention`.
@@ -132,9 +132,9 @@ When processing a row, ClickHouse checks the rules in the `pattern` sections. Ea
 
 Fields for `pattern` and `default` sections:
 
--   `rule_type` - a rule's type. It's applied only to a particular metrics. The engine use it to separate plain and tagged metrics. Optional parameter. Default value: `all`.  
-It's unnecessary when performance is not critical, or only one metrics type is used, e.g. plain metrics. By default only one type of rules set is created. Otherwise, if any of special types is defined, two different sets are created. One for plain metrics (root.branch.leaf) and one for tagged metrics (root.branch.leaf;tag1=value1).  
-The default rules are ended up in both sets.  
+-   `rule_type` - a rule's type. It's applied only to a particular metrics. The engine use it to separate plain and tagged metrics. Optional parameter. Default value: `all`.
+It's unnecessary when performance is not critical, or only one metrics type is used, e.g. plain metrics. By default only one type of rules set is created. Otherwise, if any of special types is defined, two different sets are created. One for plain metrics (root.branch.leaf) and one for tagged metrics (root.branch.leaf;tag1=value1).
+The default rules are ended up in both sets.
 Valid values:
     -   `all` (default) - a universal rule, used when `rule_type` is omitted.
     -   `plain` - a rule for plain metrics. The field `regexp` is processed as regular expression.
@@ -143,7 +143,7 @@ Valid values:
 -   `regexp` – A pattern for the metric name (a regular or DSL).
 -   `age` – The minimum age of the data in seconds.
 -   `precision`– How precisely to define the age of the data in seconds. Should be a divisor for 86400 (seconds in a day).
--   `function` – The name of the aggregating function to apply to data whose age falls within the range `[age, age + precision]`. Accepted functions: min / max / any / avg. The average is calculated imprecisely, like the average of the averages. 
+-   `function` – The name of the aggregating function to apply to data whose age falls within the range `[age, age + precision]`. Accepted functions: min / max / any / avg. The average is calculated imprecisely, like the average of the averages.
 
 ### Configuration Example without rules types {#configuration-example}
 

docs/en/engines/table-engines/mergetree-family/index.md

@@ -3,7 +3,7 @@ sidebar_position: 10
 sidebar_label: MergeTree Family
 ---
 
-# MergeTree Engine Family {#mergetree-engine-family}
+# MergeTree Engine Family
 
 Table engines from the MergeTree family are the core of ClickHouse data storage capabilities. They provide most features for resilience and high-performance data retrieval: columnar storage, custom partitioning, sparse primary index, secondary data-skipping indexes, etc.
 

docs/en/engines/table-engines/mergetree-family/mergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 11
 sidebar_label:  MergeTree
 ---
 
-# MergeTree {#table_engines-mergetree}
+# MergeTree
 
 The `MergeTree` engine and other engines of this family (`*MergeTree`) are the most robust ClickHouse table engines.
 
@@ -694,7 +694,7 @@ Tags:
 -   `volume_name_N` — Volume name. Volume names must be unique.
 -   `disk` — a disk within a volume.
 -   `max_data_part_size_bytes` — the maximum size of a part that can be stored on any of the volume’s disks. If the a size of a merged part estimated to be bigger than `max_data_part_size_bytes` then this part will be written to a next volume. Basically this feature allows to keep new/small parts on a hot (SSD) volume and move them to a cold (HDD) volume when they reach large size. Do not use this setting if your policy has only one volume.
--   `move_factor` — when the amount of available space gets lower than this factor, data automatically starts to move on the next volume if any (by default, 0.1). ClickHouse sorts existing parts by size from largest to smallest (in descending order) and selects parts with the total size that is sufficient to meet the `move_factor` condition. If the total size of all parts is insufficient, all parts will be moved. 
+-   `move_factor` — when the amount of available space gets lower than this factor, data automatically starts to move on the next volume if any (by default, 0.1). ClickHouse sorts existing parts by size from largest to smallest (in descending order) and selects parts with the total size that is sufficient to meet the `move_factor` condition. If the total size of all parts is insufficient, all parts will be moved.
 -   `prefer_not_to_merge` — Disables merging of data parts on this volume. When this setting is enabled, merging data on this volume is not allowed. This allows controlling how ClickHouse works with slow disks.
 -   `perform_ttl_move_on_insert` — Disables TTL move on data part INSERT. By default if we insert a data part that already expired by the TTL move rule it immediately goes to a volume/disk declared in move rule. This can significantly slowdown insert in case if destination volume/disk is slow (e.g. S3).
 -   `load_balancing` - Policy for disk balancing, `round_robin` or `least_used`.

docs/en/engines/table-engines/mergetree-family/replacingmergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 40
 sidebar_label:  ReplacingMergeTree
 ---
 
-# ReplacingMergeTree {#replacingmergetree}
+# ReplacingMergeTree
 
 The engine differs from [MergeTree](../../../engines/table-engines/mergetree-family/mergetree.md#table_engines-mergetree) in that it removes duplicate entries with the same [sorting key](../../../engines/table-engines/mergetree-family/mergetree.md) value (`ORDER BY` table section, not `PRIMARY KEY`).
 

docs/en/engines/table-engines/mergetree-family/replication.md

@@ -3,7 +3,7 @@ sidebar_position: 20
 sidebar_label: Data Replication
 ---
 
-# Data Replication {#table_engines-replication}
+# Data Replication
 
 Replication is only supported for tables in the MergeTree family:
 
@@ -112,7 +112,7 @@ Data blocks are deduplicated. For multiple writes of the same data block (data b
 
 During replication, only the source data to insert is transferred over the network. Further data transformation (merging) is coordinated and performed on all the replicas in the same way. This minimizes network usage, which means that replication works well when replicas reside in different datacenters. (Note that duplicating data in different datacenters is the main goal of replication.)
 
-You can have any number of replicas of the same data. Based on our experiences, a relatively reliable and convenient solution could use double replication in production, with each server using RAID-5 or RAID-6 (and RAID-10 in some cases). 
+You can have any number of replicas of the same data. Based on our experiences, a relatively reliable and convenient solution could use double replication in production, with each server using RAID-5 or RAID-6 (and RAID-10 in some cases).
 
 The system monitors data synchronicity on replicas and is able to recover after a failure. Failover is automatic (for small differences in data) or semi-automatic (when data differs too much, which may indicate a configuration error).
 

docs/en/engines/table-engines/mergetree-family/summingmergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 50
 sidebar_label:  SummingMergeTree
 ---
 
-# SummingMergeTree {#summingmergetree}
+# SummingMergeTree
 
 The engine inherits from [MergeTree](../../../engines/table-engines/mergetree-family/mergetree.md#table_engines-mergetree). The difference is that when merging data parts for `SummingMergeTree` tables ClickHouse replaces all the rows with the same primary key (or more accurately, with the same [sorting key](../../../engines/table-engines/mergetree-family/mergetree.md)) with one row which contains summarized values for the columns with the numeric data type. If the sorting key is composed in a way that a single key value corresponds to large number of rows, this significantly reduces storage volume and speeds up data selection.
 

docs/en/engines/table-engines/mergetree-family/versionedcollapsingmergetree.md

@@ -3,7 +3,7 @@ sidebar_position: 80
 sidebar_label:  VersionedCollapsingMergeTree
 ---
 
-# VersionedCollapsingMergeTree {#versionedcollapsingmergetree}
+# VersionedCollapsingMergeTree
 
 This engine:
 
@@ -53,7 +53,7 @@ When creating a `VersionedCollapsingMergeTree` table, the same [clauses](../../.
 
 <summary>Deprecated Method for Creating a Table</summary>
 
-:::warning    
+:::warning
 Do not use this method in new projects. If possible, switch old projects to the method described above.
 :::
 

docs/en/engines/table-engines/special/buffer.md

@@ -3,7 +3,7 @@ sidebar_position: 120
 sidebar_label:  Buffer
 ---
 
-# Buffer Table Engine {#buffer}
+# Buffer Table Engine
 
 Buffers the data to write in RAM, periodically flushing it to another table. During the read operation, data is read from the buffer and the other table simultaneously.
 
@@ -54,7 +54,7 @@ If the set of columns in the Buffer table does not match the set of columns in a
 If the types do not match for one of the columns in the Buffer table and a subordinate table, an error message is entered in the server log, and the buffer is cleared.
 The same thing happens if the subordinate table does not exist when the buffer is flushed.
 
-:::warning    
+:::warning
 Running ALTER on the Buffer table in releases made before 26 Oct 2021 will cause a `Block structure mismatch` error (see [#15117](https://github.com/ClickHouse/ClickHouse/issues/15117) and [#30565](https://github.com/ClickHouse/ClickHouse/pull/30565)), so deleting the Buffer table and then recreating is the only option. It is advisable to check that this error is fixed in your release before trying to run ALTER on the Buffer table.
 :::
 

docs/en/engines/table-engines/special/dictionary.md

@@ -3,7 +3,7 @@ sidebar_position: 20
 sidebar_label: Dictionary
 ---
 
-# Dictionary Table Engine {#dictionary}
+# Dictionary Table Engine
 
 The `Dictionary` engine displays the [dictionary](../../../sql-reference/dictionaries/external-dictionaries/external-dicts.md) data as a ClickHouse table.
 

docs/en/engines/table-engines/special/distributed.md

@@ -3,7 +3,7 @@ sidebar_position: 10
 sidebar_label: Distributed
 ---
 
-# Distributed Table Engine {#distributed}
+# Distributed Table Engine
 
 Tables with Distributed engine do not store any data of their own, but allow distributed query processing on multiple servers.
 Reading is automatically parallelized. During a read, the table indexes on remote servers are used, if there are any.
@@ -209,13 +209,13 @@ When querying a `Distributed` table, `SELECT` queries are sent to all shards and
 
 When the `max_parallel_replicas` option is enabled, query processing is parallelized across all replicas within a single shard. For more information, see the section [max_parallel_replicas](../../../operations/settings/settings.md#settings-max_parallel_replicas).
 
-To learn more about how distibuted `in` and `global in` queries are processed, refer to [this](../../../sql-reference/operators/in.md#select-distributed-subqueries) documentation. 
+To learn more about how distibuted `in` and `global in` queries are processed, refer to [this](../../../sql-reference/operators/in.md#select-distributed-subqueries) documentation.
 
 ## Virtual Columns {#virtual-columns}
 
 -   `_shard_num` — Contains the `shard_num` value from the table `system.clusters`. Type: [UInt32](../../../sql-reference/data-types/int-uint.md).
 
-:::note    
+:::note
 Since [remote](../../../sql-reference/table-functions/remote.md) and [cluster](../../../sql-reference/table-functions/cluster.md) table functions internally create temporary Distributed table, `_shard_num` is available there too.
 :::
 

docs/en/engines/table-engines/special/external-data.md

@@ -3,7 +3,7 @@ sidebar_position: 130
 sidebar_label: External Data
 ---
 
-# External Data for Query Processing {#external-data-for-query-processing}
+# External Data for Query Processing
 
 ClickHouse allows sending a server the data that is needed for processing a query, together with a `SELECT` query. This data is put in a temporary table (see the section “Temporary tables”) and can be used in the query (for example, in `IN` operators).
 

docs/en/engines/table-engines/special/file.md

@@ -3,7 +3,7 @@ sidebar_position: 40
 sidebar_label:  File
 ---
 
-# File Table Engine {#table_engines-file}
+# File Table Engine
 
 The File table engine keeps the data in a file in one of the supported [file formats](../../../interfaces/formats.md#formats) (`TabSeparated`, `Native`, etc.).
 

docs/en/engines/table-engines/special/generate.md

@@ -3,7 +3,7 @@ sidebar_position: 140
 sidebar_label:  GenerateRandom
 ---
 
-# GenerateRandom Table Engine {#table_engines-generate}
+# GenerateRandom Table Engine
 
 The GenerateRandom table engine produces random data for given table schema.
 

docs/en/engines/table-engines/special/index.md

@@ -3,7 +3,7 @@ sidebar_position: 50
 sidebar_label: Special
 ---
 
-# Special Table Engines {#special-table-engines}
+# Special Table Engines
 
 There are three main categories of table engines:
 

docs/en/engines/table-engines/special/join.md

@@ -3,7 +3,7 @@ sidebar_position: 70
 sidebar_label: Join
 ---
 
-# Join Table Engine {#join}
+# Join Table Engine
 
 Optional prepared data structure for usage in [JOIN](../../../sql-reference/statements/select/join.md#select-join) operations.
 

docs/en/engines/table-engines/special/materializedview.md

@@ -3,7 +3,7 @@ sidebar_position: 100
 sidebar_label: MaterializedView
 ---
 
-# MaterializedView Table Engine {#materializedview}
+# MaterializedView Table Engine
 
 Used for implementing materialized views (for more information, see [CREATE VIEW](../../../sql-reference/statements/create/view.md#materialized)). For storing data, it uses a different engine that was specified when creating the view. When reading from a table, it just uses that engine.
 

docs/en/engines/table-engines/special/memory.md

@@ -3,7 +3,7 @@ sidebar_position: 110
 sidebar_label:  Memory
 ---
 
-# Memory Table Engine {#memory}
+# Memory Table Engine
 
 The Memory engine stores data in RAM, in uncompressed form. Data is stored in exactly the same form as it is received when read. In other words, reading from this table is completely free.
 Concurrent data access is synchronized. Locks are short: read and write operations do not block each other.

docs/en/engines/table-engines/special/merge.md

@@ -3,7 +3,7 @@ sidebar_position: 30
 sidebar_label: Merge
 ---
 
-# Merge Table Engine {#merge}
+# Merge Table Engine
 
 The `Merge` engine (not to be confused with `MergeTree`) does not store data itself, but allows reading from any number of other tables simultaneously.
 
@@ -18,7 +18,7 @@ CREATE TABLE ... Engine=Merge(db_name, tables_regexp)
 **Engine Parameters**
 
 - `db_name` — Possible values:
-    - database name, 
+    - database name,
     - constant expression that returns a string with a database name, for example, `currentDatabase()`,
     - `REGEXP(expression)`, where `expression` is a regular expression to match the DB names.
 
@@ -49,11 +49,11 @@ CREATE TABLE all_visitors (id UInt32) ENGINE=Merge(REGEXP('ABC_*'), 'visitors');
 Let's say you have an old table `WatchLog_old` and decided to change partitioning without moving data to a new table `WatchLog_new`, and you need to see data from both tables.
 
 ``` sql
-CREATE TABLE WatchLog_old(date Date, UserId Int64, EventType String, Cnt UInt64) 
+CREATE TABLE WatchLog_old(date Date, UserId Int64, EventType String, Cnt UInt64)
     ENGINE=MergeTree(date, (UserId, EventType), 8192);
 INSERT INTO WatchLog_old VALUES ('2018-01-01', 1, 'hit', 3);
 
-CREATE TABLE WatchLog_new(date Date, UserId Int64, EventType String, Cnt UInt64) 
+CREATE TABLE WatchLog_new(date Date, UserId Int64, EventType String, Cnt UInt64)
     ENGINE=MergeTree PARTITION BY date ORDER BY (UserId, EventType) SETTINGS index_granularity=8192;
 INSERT INTO WatchLog_new VALUES ('2018-01-02', 2, 'hit', 3);
 

docs/en/engines/table-engines/special/null.md

@@ -3,7 +3,7 @@ sidebar_position: 50
 sidebar_label:  'Null'
 ---
 
-# Null Table Engine {#null}
+# Null Table Engine
 
 When writing to a `Null` table, data is ignored. When reading from a `Null` table, the response is empty.
 

docs/en/engines/table-engines/special/set.md

@@ -3,7 +3,7 @@ sidebar_position: 60
 sidebar_label: Set
 ---
 
-# Set Table Engine {#set}
+# Set Table Engine
 
 A data set that is always in RAM. It is intended for use on the right side of the `IN` operator (see the section “IN operators”).
 

docs/en/engines/table-engines/special/url.md

@@ -3,7 +3,7 @@ sidebar_position: 80
 sidebar_label:  URL
 ---
 
-# URL Table Engine {#table_engines-url}
+# URL Table Engine
 
 Queries data to/from a remote HTTP/HTTPS server. This engine is similar to the [File](../../../engines/table-engines/special/file.md) engine.
 
@@ -13,10 +13,10 @@ Syntax: `URL(URL [,Format] [,CompressionMethod])`
 
 - The `Format` must be one that ClickHouse can use in `SELECT` queries and, if necessary, in `INSERTs`. For the full list of supported formats, see [Formats](../../../interfaces/formats.md#formats).
 
-- `CompressionMethod` indicates that whether the HTTP body should be compressed. If the compression is enabled, the HTTP packets sent by the URL engine contain 'Content-Encoding' header to indicate which compression method is used. 
+- `CompressionMethod` indicates that whether the HTTP body should be compressed. If the compression is enabled, the HTTP packets sent by the URL engine contain 'Content-Encoding' header to indicate which compression method is used.
 
 To enable compression, please first make sure the remote HTTP endpoint indicated by the `URL` parameter supports corresponding compression algorithm.
-   
+
 The supported `CompressionMethod` should be one of following:
 - gzip or gz
 - deflate

docs/en/engines/table-engines/special/view.md

@@ -3,7 +3,7 @@ sidebar_position: 90
 sidebar_label:  View
 ---
 
-# View Table Engine {#table_engines-view}
+# View Table Engine
 
 Used for implementing views (for more information, see the `CREATE VIEW query`). It does not store data, but only stores the specified `SELECT` query. When reading from a table, it runs this query (and deletes all unnecessary columns from the query).
 

docs/en/getting-started/example-datasets/amplab-benchmark.md

@@ -3,7 +3,7 @@ sidebar_label: AMPLab Big Data Benchmark
 description: A benchmark dataset used for comparing the performance of data warehousing solutions.
 ---
 
-# AMPLab Big Data Benchmark {#amplab-big-data-benchmark}
+# AMPLab Big Data Benchmark
 
 See https://amplab.cs.berkeley.edu/benchmark/
 

docs/en/getting-started/install.md

@@ -6,7 +6,7 @@ description: ClickHouse can run on any Linux, FreeBSD, or Mac OS X with x86_64,
 slug: /en/getting-started/install
 ---
 
-# Installation {#installation}
+# Installation
 
 ## System Requirements {#system-requirements}
 
@@ -70,7 +70,7 @@ You can also download and install packages manually from [here](https://packages
 -   `clickhouse-client` — Creates a symbolic link for `clickhouse-client` and other client-related tools. and installs client configuration files.
 -   `clickhouse-common-static-dbg` — Installs ClickHouse compiled binary files with debug info.
 
-:::info    
+:::info
 If you need to install specific version of ClickHouse you have to install all packages with the same version:
 `sudo apt-get install clickhouse-server=21.8.5.7 clickhouse-client=21.8.5.7 clickhouse-common-static=21.8.5.7`
 :::
@@ -190,22 +190,22 @@ sudo ./clickhouse install
 
 ### From Precompiled Binaries for Non-Standard Environments {#from-binaries-non-linux}
 
-For non-Linux operating systems and for AArch64 CPU arhitecture, ClickHouse builds are provided as a cross-compiled binary from the latest commit of the `master` branch (with a few hours delay). 
+For non-Linux operating systems and for AArch64 CPU arhitecture, ClickHouse builds are provided as a cross-compiled binary from the latest commit of the `master` branch (with a few hours delay).
 
 
 -   [MacOS x86_64](https://builds.clickhouse.com/master/macos/clickhouse)
      ```bash
      curl -O 'https://builds.clickhouse.com/master/macos/clickhouse' && chmod a+x ./clickhouse
      ```
--   [MacOS Aarch64 (Apple Silicon)](https://builds.clickhouse.com/master/macos-aarch64/clickhouse) 
+-   [MacOS Aarch64 (Apple Silicon)](https://builds.clickhouse.com/master/macos-aarch64/clickhouse)
     ```bash
     curl -O 'https://builds.clickhouse.com/master/macos-aarch64/clickhouse' && chmod a+x ./clickhouse
     ```
--   [FreeBSD x86_64](https://builds.clickhouse.com/master/freebsd/clickhouse) 
+-   [FreeBSD x86_64](https://builds.clickhouse.com/master/freebsd/clickhouse)
     ```bash
     curl -O 'https://builds.clickhouse.com/master/freebsd/clickhouse' && chmod a+x ./clickhouse
     ```
--   [Linux AArch64](https://builds.clickhouse.com/master/aarch64/clickhouse) 
+-   [Linux AArch64](https://builds.clickhouse.com/master/aarch64/clickhouse)
     ```bash
     curl -O 'https://builds.clickhouse.com/master/aarch64/clickhouse' && chmod a+x ./clickhouse
     ```

docs/en/getting-started/playground.md

@@ -6,7 +6,7 @@ description: The ClickHouse Playground allows people to experiment with ClickHou
 slug: /en/getting-started/playground
 ---
 
-# ClickHouse Playground {#clickhouse-playground}
+# ClickHouse Playground
 
 [ClickHouse Playground](https://play.clickhouse.com/play?user=play) allows people to experiment with ClickHouse by running queries instantly, without setting up their server or cluster.
 Several example datasets are available in Playground.

docs/en/interfaces/cli.md

@@ -3,7 +3,7 @@ sidebar_position: 17
 sidebar_label: Command-Line Client
 ---
 
-# Command-line Client {#command-line-client}
+# Command-line Client
 
 ClickHouse provides a native command-line client: `clickhouse-client`. The client supports command-line options and configuration files. For more information, see [Configuring](#interfaces_cli_configuration).
 

docs/en/interfaces/cpp.md

@@ -3,7 +3,7 @@ sidebar_position: 24
 sidebar_label: C++ Client Library
 ---
 
-# C++ Client Library {#c-client-library}
+# C++ Client Library
 
 See README at [clickhouse-cpp](https://github.com/ClickHouse/clickhouse-cpp) repository.
 

docs/en/interfaces/formats.md

@@ -3,7 +3,7 @@ sidebar_position: 21
 sidebar_label: Input and Output Formats
 ---
 
-# Formats for Input and Output Data {#formats}
+# Formats for Input and Output Data
 
 ClickHouse can accept and return data in various formats. A format supported for input can be used to parse the data provided to `INSERT`s, to perform `SELECT`s from a file-backed table such as File, URL or HDFS, or to read an external dictionary. A format supported for output can be used to arrange the
 results of a `SELECT`, and to perform `INSERT`s into a file-backed table.
@@ -625,7 +625,7 @@ Example:
                         "name": "str",
                         "type": "String"
                 },
-               
+
                 {
                         "name": "arr",
                         "type": "Array(UInt8)"

docs/en/interfaces/grpc.md

@@ -3,19 +3,19 @@ sidebar_position: 19
 sidebar_label: gRPC Interface
 ---
 
-# gRPC Interface {#grpc-interface}
+# gRPC Interface
 
 ## Introduction {#grpc-interface-introduction}
 
 ClickHouse supports [gRPC](https://grpc.io/) interface. It is an open source remote procedure call system that uses HTTP/2 and [Protocol Buffers](https://en.wikipedia.org/wiki/Protocol_Buffers). The implementation of gRPC in ClickHouse supports:
 
--   SSL; 
--   authentication; 
--   sessions; 
--   compression; 
--   parallel queries through the same channel; 
--   cancellation of queries; 
--   getting progress and logs; 
+-   SSL;
+-   authentication;
+-   sessions;
+-   compression;
+-   parallel queries through the same channel;
+-   cancellation of queries;
+-   getting progress and logs;
 -   external tables.
 
 The specification of the interface is described in [clickhouse_grpc.proto](https://github.com/ClickHouse/ClickHouse/blob/master/src/Server/grpc_protos/clickhouse_grpc.proto).
@@ -59,7 +59,7 @@ To use the gRPC interface set `grpc_port` in the main [server configuration](../
 ## Built-in Client {#grpc-client}
 
 You can write a client in any of the programming languages supported by gRPC using the provided [specification](https://github.com/ClickHouse/ClickHouse/blob/master/src/Server/grpc_protos/clickhouse_grpc.proto).
-Or you can use a built-in Python client. It is placed in [utils/grpc-client/clickhouse-grpc-client.py](https://github.com/ClickHouse/ClickHouse/blob/master/utils/grpc-client/clickhouse-grpc-client.py) in the repository. The built-in client requires [grpcio and grpcio-tools](https://grpc.io/docs/languages/python/quickstart) Python modules. 
+Or you can use a built-in Python client. It is placed in [utils/grpc-client/clickhouse-grpc-client.py](https://github.com/ClickHouse/ClickHouse/blob/master/utils/grpc-client/clickhouse-grpc-client.py) in the repository. The built-in client requires [grpcio and grpcio-tools](https://grpc.io/docs/languages/python/quickstart) Python modules.
 
 The client supports the following arguments:
 

docs/en/interfaces/http.md

@@ -3,7 +3,7 @@ sidebar_position: 19
 sidebar_label: HTTP Interface
 ---
 
-# HTTP Interface {#http-interface}
+# HTTP Interface
 
 The HTTP interface lets you use ClickHouse on any platform from any programming language in a form of REST API. The HTTP interface is more limited than the native interface, but it has better language support.
 
@@ -178,7 +178,7 @@ You can also choose to use [HTTP compression](https://en.wikipedia.org/wiki/HTTP
 To send a compressed `POST` request, append the request header `Content-Encoding: compression_method`.
 In order for ClickHouse to compress the response, enable compression with [enable_http_compression](../operations/settings/settings.md#settings-enable_http_compression) setting and append `Accept-Encoding: compression_method` header to the request. You can configure the data compression level in the [http_zlib_compression_level](../operations/settings/settings.md#settings-http_zlib_compression_level) setting for all compression methods.
 
-:::info    
+:::info
 Some HTTP clients might decompress data from the server by default (with `gzip` and `deflate`) and you might get decompressed data even if you use the compression settings correctly.
 :::
 

docs/en/interfaces/jdbc.md

@@ -3,7 +3,7 @@ sidebar_position: 22
 sidebar_label: JDBC Driver
 ---
 
-# JDBC Driver {#jdbc-driver}
+# JDBC Driver
 
 Use the [official JDBC driver](https://github.com/ClickHouse/clickhouse-jdbc) (and Java client) to access ClickHouse from your Java applications.
 

docs/en/interfaces/mysql.md

@@ -3,7 +3,7 @@ sidebar_position: 20
 sidebar_label: MySQL Interface
 ---
 
-# MySQL Interface {#mysql-interface}
+# MySQL Interface
 
 ClickHouse supports MySQL wire protocol. It can be enabled by [mysql_port](../operations/server-configuration-parameters/settings.md#server_configuration_parameters-mysql_port) setting in configuration file:
 

docs/en/interfaces/odbc.md

@@ -3,10 +3,10 @@ sidebar_position: 23
 sidebar_label: ODBC Driver
 ---
 
-# ODBC Driver {#odbc-driver}
+# ODBC Driver
 
 Use the [official ODBC driver](https://github.com/ClickHouse/clickhouse-odbc) for accessing ClickHouse as a data source.
 
-  
+
 
 [Original article](https://clickhouse.com/docs/en/interfaces/odbc/) <!--hide-->

docs/en/interfaces/overview.md

@@ -5,7 +5,7 @@ keywords: [clickhouse, network, interfaces, http, tcp, grpc, command-line, clien
 description: ClickHouse provides three network interfaces
 ---
 
-# Interfaces {#interfaces}
+# Interfaces
 
 ClickHouse provides three network interfaces (they can be optionally wrapped in TLS for additional security):
 

docs/en/interfaces/tcp.md

@@ -3,7 +3,7 @@ sidebar_position: 18
 sidebar_label: Native Interface (TCP)
 ---
 
-# Native Interface (TCP) {#native-interface-tcp}
+# Native Interface (TCP)
 
 The native protocol is used in the [command-line client](../interfaces/cli.md), for inter-server communication during distributed query processing, and also in other C++ programs. Unfortunately, native ClickHouse protocol does not have formal specification yet, but it can be reverse-engineered from ClickHouse source code (starting [around here](https://github.com/ClickHouse/ClickHouse/tree/master/src/Client)) and/or by intercepting and analyzing TCP traffic.
 

docs/en/interfaces/third-party/client-libraries.md

@@ -3,9 +3,9 @@ sidebar_position: 26
 sidebar_label: Client Libraries
 ---
 
-# Client Libraries from Third-party Developers {#client-libraries-from-third-party-developers}
+# Client Libraries from Third-party Developers
 
-:::warning    
+:::warning
 ClickHouse Inc does **not** maintain the libraries listed below and hasn’t done any extensive testing to ensure their quality.
 :::
 

docs/en/interfaces/third-party/gui.md

@@ -3,7 +3,7 @@ sidebar_position: 28
 sidebar_label: Visual Interfaces
 ---
 
-# Visual Interfaces from Third-party Developers {#visual-interfaces-from-third-party-developers}
+# Visual Interfaces from Third-party Developers
 
 ## Open-Source {#open-source}
 
@@ -249,7 +249,7 @@ Features:
 - Web-based interface.
 
 TABLUM.IO can be run as a self-hosted solution (as a docker image) or in the cloud.
-License: [commercial](https://tablum.io/pricing) product with 3-month free period. 
+License: [commercial](https://tablum.io/pricing) product with 3-month free period.
 
 Try it out for free [in the cloud](https://tablum.io/try).
 Learn more about the product at [TABLUM.IO](https://tablum.io/)

docs/en/interfaces/third-party/index.md

@@ -3,7 +3,7 @@ toc_folder_title: Third-Party
 sidebar_position: 24
 ---
 
-# Third-Party Interfaces {#third-party-interfaces}
+# Third-Party Interfaces
 
 This is a collection of links to third-party tools that provide some sort of interface to ClickHouse. It can be either visual interface, command-line interface or an API:
 

docs/en/interfaces/third-party/integrations.md

@@ -3,7 +3,7 @@ sidebar_position: 27
 sidebar_label: Integrations
 ---
 
-# Integration Libraries from Third-party Developers {#integration-libraries-from-third-party-developers}
+# Integration Libraries from Third-party Developers
 
 :::warning Disclaimer
 ClickHouse, Inc. does **not** maintain the tools and libraries listed below and haven’t done extensive testing to ensure their quality.

docs/en/interfaces/third-party/proxy.md

@@ -3,7 +3,7 @@ sidebar_position: 29
 sidebar_label: Proxies
 ---
 
-# Proxy Servers from Third-party Developers {#proxy-servers-from-third-party-developers}
+# Proxy Servers from Third-party Developers
 
 ## chproxy {#chproxy}
 

docs/en/operations/access-rights.md

@@ -3,7 +3,7 @@ sidebar_position: 48
 sidebar_label: Access Control and Account Management
 ---
 
-# Access Control and Account Management {#access-control}
+# Access Control and Account Management
 
 ClickHouse supports access control management based on [RBAC](https://en.wikipedia.org/wiki/Role-based_access_control) approach.
 
@@ -24,7 +24,7 @@ You can configure access entities using:
 
 We recommend using SQL-driven workflow. Both of the configuration methods work simultaneously, so if you use the server configuration files for managing accounts and access rights, you can smoothly switch to SQL-driven workflow.
 
-:::warning    
+:::warning
 You can’t manage the same access entity by both configuration methods simultaneously.
 :::
 
@@ -102,7 +102,7 @@ Privileges can be granted to a role by the [GRANT](../sql-reference/statements/g
 
 Row policy is a filter that defines which of the rows are available to a user or a role. Row policy contains filters for one particular table, as well as a list of roles and/or users which should use this row policy.
 
-:::warning    
+:::warning
 Row policies makes sense only for users with readonly access. If user can modify table or copy partitions between tables, it defeats the restrictions of row policies.
 :::
 

docs/en/operations/backup.md

@@ -3,7 +3,7 @@ sidebar_position: 49
 sidebar_label: Data Backup
 ---
 
-# Data Backup {#data-backup}
+# Data Backup
 
 While [replication](../engines/table-engines/mergetree-family/replication.md) provides protection from hardware failures, it does not protect against human errors: accidental deletion of data, deletion of the wrong table or a table on the wrong cluster, and software bugs that result in incorrect data processing or data corruption. In many cases mistakes like these will affect all replicas. ClickHouse has built-in safeguards to prevent some types of mistakes — for example, by default [you can’t just drop tables with a MergeTree-like engine containing more than 50 Gb of data](server-configuration-parameters/settings.md#max-table-size-to-drop). However, these safeguards do not cover all possible cases and can be circumvented.
 
@@ -11,7 +11,7 @@ In order to effectively mitigate possible human errors, you should carefully pre
 
 Each company has different resources available and business requirements, so there’s no universal solution for ClickHouse backups and restores that will fit every situation. What works for one gigabyte of data likely won’t work for tens of petabytes. There are a variety of possible approaches with their own pros and cons, which will be discussed below. It is a good idea to use several approaches instead of just one in order to compensate for their various shortcomings.
 
-:::note    
+:::note
 Keep in mind that if you backed something up and never tried to restore it, chances are that restore will not work properly when you actually need it (or at least it will take longer than business can tolerate). So whatever backup approach you choose, make sure to automate the restore process as well, and practice it on a spare ClickHouse cluster regularly.
 :::
 

docs/en/operations/caches.md

@@ -3,7 +3,7 @@ sidebar_position: 65
 sidebar_label: Caches
 ---
 
-# Cache Types {#cache-types}
+# Cache Types
 
 When performing queries, ClickHouse uses different caches.
 

docs/en/operations/clickhouse-keeper.md

@@ -3,7 +3,7 @@ sidebar_position: 66
 sidebar_label: ClickHouse Keeper
 ---
 
-# ClickHouse Keeper {#clickHouse-keeper}
+# ClickHouse Keeper
 
 ClickHouse Keeper provides the coordination system for data [replication](../engines/table-engines/mergetree-family/replication.md) and [distributed DDL](../sql-reference/distributed-ddl.md) queries execution. ClickHouse Keeper is compatible with ZooKeeper.
 

docs/en/operations/configuration-files.md

@@ -3,7 +3,7 @@ sidebar_position: 50
 sidebar_label: Configuration Files
 ---
 
-# Configuration Files {#configuration_files}
+# Configuration Files
 
 ClickHouse supports multi-file configuration management. The main server configuration file is `/etc/clickhouse-server/config.xml` or `/etc/clickhouse-server/config.yaml`. Other files must be in the `/etc/clickhouse-server/config.d` directory. Note, that any configuration file can be written either in XML or YAML, but mixing formats in one file is not supported. For example, you can have main configs as `config.xml` and `users.xml` and write additional files in `config.d` and `users.d` directories in `.yaml`.
 

docs/en/operations/external-authenticators/kerberos.md

@@ -1,4 +1,4 @@
-# Kerberos {#external-authenticators-kerberos}
+# Kerberos
 
 Existing and properly configured ClickHouse users can be authenticated via Kerberos authentication protocol.
 
@@ -99,7 +99,7 @@ Example (goes into `users.xml`):
 Note that Kerberos authentication cannot be used alongside with any other authentication mechanism. The presence of any other sections like `password` alongside `kerberos` will force ClickHouse to shutdown.
 :::
 
-:::info Reminder    
+:::info Reminder
 Note, that now, once user `my_user` uses `kerberos`, Kerberos must be enabled in the main `config.xml` file as described previously.
 :::
 

docs/en/operations/external-authenticators/ldap.md

@@ -1,4 +1,4 @@
-# LDAP {#external-authenticators-ldap}
+# LDAP
 
 LDAP server can be used to authenticate ClickHouse users. There are two different approaches for doing this:
 

docs/en/operations/external-authenticators/ssl-x509.md

@@ -1,4 +1,4 @@
-# SSL X.509 certificate authentication {#ssl-external-authentication}
+# SSL X.509 certificate authentication
 
 [SSL 'strict' option](../server-configuration-parameters/settings.md#server_configuration_parameters-openssl) enables mandatory certificate validation for the incoming connections. In this case, only connections with trusted certificates can be established. Connections with untrusted certificates will be rejected. Thus, certificate validation allows to uniquely authenticate an incoming connection. `Common Name` field of the certificate is used to identify connected user. This allows to associate multiple certificates with the same user. Additionally, reissuing and revoking of the certificates does not affect the ClickHouse configuration.
 

docs/en/operations/monitoring.md

@@ -3,7 +3,7 @@ sidebar_position: 45
 sidebar_label: Monitoring
 ---
 
-# Monitoring {#monitoring}
+# Monitoring
 
 You can monitor: