Merge branch 'main' of https://github.com/ClickHouse/clickhouse-docs into lang_header

Author: Blargian

README.md

@@ -171,28 +171,28 @@ Have you noticed a typo or found some wonky formatting? For small contributions
 
 1. Each page in Clickhouse.com/docs has an **Edit this page** link at the top:
 
-    ![The ClickHouse Docs website with the edit button highlighted.](./images/readme-edit-this-page.png)
+    ![The ClickHouse Docs website with the edit button highlighted.](./static/images/contribute/readme-edit-this-page.png)
 
     Click this button to edit this page in GitHub.
 
 1. Once you're in GitHub, click the pencil icon to edit this page:
 
-    ![README Pencil Icon](./images/readme-pencil-icon.png)
+    ![README Pencil Icon](./static/images/contribute/readme-pencil-icon.png)
 
 1. GitHub will _fork_ the repository for you. This creates a copy of the `clickhouse-docs` repository on your personal GitHub account.
 1. Make your changes in the textbox. Once you're done, click **Commit changes**:
 
-    ![README Commit Changes](./images/readme-commit-changes.png)
+    ![README Commit Changes](./static/images/contribute/readme-commit-changes.png)
 
 1. In the **Propose changes** popup, enter a descriptive title to explain the changes you just made. Keep this title to 10 words or less. If your changes are fairly complex and need further explanation, enter your comments into the **Extended description** field.
 1. Make sure **Create a new branch** is selected, and click **Propose changes**:
 
-    ![README Propose Changes](./images/readme-propose-changes.png)
+    ![README Propose Changes](./static/images/contribute/readme-propose-changes.png)
 
 1. A new page should open with a new pull request. Double-check that the title and description are accurate.
 1. If you've spoken to someone on the docs team about your changes, tag them into the **Reviewers** section:
 
-    ![README Create Pull Request](./images/readme-create-pull-request.png)
+    ![README Create Pull Request](./static/images/contribute/readme-create-pull-request.png)
 
     If you haven't mentioned your changes to anyone yet, leave the **Reviewers** section blank.
 

docs/best-practices/partionning_keys.md renamed to docs/best-practices/partitioning_keys.mdx

@@ -11,18 +11,20 @@ While ClickHouse is known for its speed and reliability, optimal performance is
 If you've run up against one of these guardrails, it's possible that you are implementing your use case in an unoptimized way. Contact our support team and we will gladly help you refine your use case to avoid exceeding the guardrails or look together at how we can increase them in a controlled manner. 
 :::
 
-- **Databases**: 1000
-- **Tables**: 5000
-- **Columns**: ∼1000 (wide format is preferred to compact)
-- **Partitions**: 50k
-- **Parts**: 100k across the entire instance
-- **Part size**: 150gb
-- **Services per organization**: 20 (soft)
-- **Services per warehouse**: 5 (soft)
-- **Low cardinality**: 10k or less
-- **Primary keys in a table**: 4-5 that sufficiently filter down the data
-- **Query concurrency**: 1000
-- **Batch ingest**: anything > 1M will be split by the system in 1M row blocks
+| Dimension | Limit |
+|-----------|-------|
+|**Databases**| 1000|
+|**Tables**| 5000|
+|**Columns**| ∼1000 (wide format is preferred to compact)|
+|**Partitions**| 50k|
+|**Parts**| 100k across the entire instance|
+|**Part size**| 150gb|
+|**Services per organization**| 20 (soft)|
+|**Services per warehouse**| 5 (soft)|
+|**Low cardinality**| 10k or less|
+|**Primary keys in a table**| 4-5 that sufficiently filter down the data|
+|**Query concurrency**| 1000|
+|**Batch ingest**| anything > 1M will be split by the system in 1M row blocks|
 
 :::note
 For Single Replica Services, the maximum number of databases is restricted to 100, and the maximum number of tables is restricted to 500. In addition, storage for Basic Tier Services is limited to 1 TB.

docs/cloud/bestpractices/usagelimits.md

@@ -5,6 +5,6 @@ title: 'Choose a Low Cardinality Partitioning Key'
 description: 'Use a low cardinality partitioning key or avoid using any partitioning key for your table.'
 ---
 
-import Content from '@site/docs/best-practices/partionning_keys.md';
+import Content from '@site/docs/best-practices/partitioning_keys.mdx';
 
 <Content />

docs/guides/best-practices/partitioningkey.md

@@ -1494,7 +1494,7 @@ A compromise between fastest retrieval and optimal data compression is to use a
 
 ### A concrete example {#a-concrete-example}
 
-One concrete example is a the plaintext paste service https://pastila.nl that Alexey Milovidov developed and [blogged about](https://clickhouse.com/blog/building-a-paste-service-with-clickhouse/).
+One concrete example is a the plaintext paste service [https://pastila.nl](https://pastila.nl) that Alexey Milovidov developed and [blogged about](https://clickhouse.com/blog/building-a-paste-service-with-clickhouse/).
 
 On every change to the text-area, the data is saved automatically into a ClickHouse table row (one row per change).
 

docs/guides/best-practices/sparse-primary-indexes.md

@@ -3,14 +3,18 @@ title: 'Adding specific tables to a ClickPipe'
 description: 'Describes the steps need to add specific tables to a ClickPipe.'
 sidebar_label: 'Add Table'
 slug: /integrations/clickpipes/postgres/add_table
+show_title: false
 ---
 
 import Image from '@theme/IdealImage';
 import add_table from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/add_table.png'
 
+# Adding specific tables to a ClickPipe
+
 There are scenarios where it would be useful to add specific tables to a pipe. This becomes a common necessity as your transactional or analytical workload scales.
 
-## Steps to add specific tables {#add-tables-steps}
+## Steps to add specific tables to a ClickPipe {#add-tables-steps}
+
 This can be done by the following steps:
 1. [Pause](./pause_and_resume.md) the pipe.
 2. Click on Edit Table settings.

docs/integrations/data-ingestion/clickpipes/postgres/add_table.md

@@ -85,6 +85,16 @@ IAM policy (Please replace `{STREAM_NAME}` with your Kinesis stream name):
             ],
             "Effect": "Allow"
         },
+        {
+            "Action": [
+                "kinesis:SubscribeToShard",
+                "kinesis:DescribeStreamConsumer"
+            ],
+            "Resource": [
+                "arn:aws:kinesis:region:account-id:stream/{STREAM_NAME}/*"
+            ],
+            "Effect": "Allow"
+        },
         {
             "Action": [
                 "kinesis:ListStreams"

docs/integrations/data-ingestion/clickpipes/secure-kinesis.md

@@ -60,10 +60,10 @@ const config = {
   // url: process.env.VERCEL_URL ? `https://${process.env.VERCEL_URL}` : 'https://bookish-disco-5997zvo.pages.github.io',
   baseUrl: "/docs/",
   baseUrlIssueBanner: true,
-  onBrokenLinks: "warn",
+  onBrokenLinks: "throw",
   onBrokenMarkdownLinks: "warn",
   onDuplicateRoutes: "throw",
-  onBrokenAnchors: "warn",
+  onBrokenAnchors: "throw",
   favicon: "img/docs_favicon.ico",
   organizationName: "ClickHouse",
   trailingSlash: false,