Merge branch 'main' into security-sept25

Author: Blargian

docs/chdb/api/python.md

@@ -27,7 +27,7 @@ You can use it when you want to get the power of ClickHouse in a programming lan
 
 chDB has the following language bindings:
 
-* [Python](install/python.md)
+* [Python](install/python.md) - [API Reference](api/python.md)
 * [Go](install/go.md)
 * [Rust](install/rust.md)
 * [NodeJS](install/nodejs.md)

docs/chdb/index.md

@@ -8,11 +8,11 @@ doc_type: 'landing-page'
 
 Instructions for how to get setup with chDB are available below for the following languages and runtimes:
 
-| Language                               |
-|----------------------------------------|
-| [Python](/chdb/install/python) |
-| [NodeJS](/chdb/install/nodejs) |
-| [Go](/chdb/install/go)         |
-| [Rust](/chdb/install/rust)     |
-| [Bun](/chdb/install/bun)       |
-| [C and C++](/chdb/install/c)   |
+| Language                               | API Reference                       |
+|----------------------------------------|-------------------------------------|
+| [Python](/chdb/install/python) | [Python API](/chdb/api/python) |
+| [NodeJS](/chdb/install/nodejs) |                                     |
+| [Go](/chdb/install/go)         |                                     |
+| [Rust](/chdb/install/rust)     |                                     |
+| [Bun](/chdb/install/bun)       |                                     |
+| [C and C++](/chdb/install/c)   |                                     |

docs/chdb/install/index.md

@@ -0,0 +1,11 @@
+---
+slug: /cloud/guides/sql-console/gather-connection-details
+sidebar_label: 'Gather your connection details'
+title: 'Gather your connection details'
+description: 'Gather your connection details'
+doc_type: 'guide'
+---
+
+import ConnectionDetails from '@site/docs/_snippets/_gather_your_details_http.mdx';
+
+<ConnectionDetails />

docs/cloud/guides/SQL_console/connection_details.md

@@ -29,6 +29,7 @@ or look together at how we can increase them in a controlled manner.
 | **Part size**                 | 150gb                                                      |
 | **Services per organization** | 20 (soft)                                                  |
 | **Services per warehouse**    | 5 (soft)                                                   |
+| **Replicas per service**      | 20 (soft)                                                  |  
 | **Low cardinality**           | 10k or less                                                |
 | **Primary keys in a table**   | 4-5 that sufficiently filter down the data                 |
 | **Query concurrency**         | 1000 (per replica)                                         |

docs/cloud/guides/best_practices/usagelimits.md

@@ -4,4 +4,7 @@ title: 'Guides'
 hide_title: true
 description: 'Table of contents page for the ClickHouse Cloud guides section'
 doc_type: 'landing-page'
----
+---
+
+<!--AUTOGENERATED_START-->
+<!--AUTOGENERATED_END-->

docs/cloud/guides/index.md

@@ -180,6 +180,10 @@ Best for: large scale, mission critical deployments that have stringent security
 
 A ClickHouse Credit is a unit of credit toward Customer's usage of ClickHouse Cloud equal to one (1) US dollar, to be applied based on ClickHouse's then-current published price list.
 
+### Where can I find legacy pricing? {#find-legacy-pricing}
+
+Legacy pricing information can be found [here](https://clickhouse.com/pricing?legacy=true).
+
 :::note 
 If you are being billed through Stripe then you will see that 1 CHC is equal to \$0.01 USD on your Stripe invoice. This is to allow accurate billing on Stripe due to their limitation on not being able to bill fractional quantities of our standard SKU of 1 CHC = \$1 USD.
 :::

docs/cloud/onboard/02_migrate/01_migration_guides/03_bigquery/_04_sql_translation_reference.md

@@ -47,8 +47,8 @@ Get started with ClickHouse Cloud on the [AWS Marketplace](https://aws.amazon.co
 
 3. On the next screen, configure the contract:
 - **Length of contract** - PAYG contracts run month to month.
-- **Renewal settings** - You can set the contract to auto renew or not. 
-Note that if you don't enable auto renewal, your organization is automatically put into a grace period at the end of the billing cycle and then decommissioned.
+- **Renewal settings** - You can set the contract to auto-renew or not.
+Note that we strongly recommend keeping your subscription set to auto-renew every month. However, if you don't enable auto renewal, your organization is automatically put into a grace period at the end of the billing cycle and then decommissioned.
 
 - **Contract options** - You can input any number (or just 1) into this text box. This will not affect the price you pay as the price for these units for the public offer is $0. These units are usually used when accepting a private offer from ClickHouse Cloud.
 

docs/cloud/reference/03_billing/01_billing_overview.md

@@ -557,11 +557,7 @@ SHOW DATABASES;
 
 ## Create a table on the cluster {#creating-a-table}
 
-Now that the database has been created, you will create a distributed table.
-Distributed tables are tables which have access to shards located on different
-hosts and are defined using the `Distributed` table engine. The distributed table
-acts as the interface across all the shards in the cluster.
-
+Now that the database has been created, you will create a table.
 Run the following query from any of the host clients:
 
 ```sql
@@ -608,8 +604,6 @@ SHOW TABLES IN uk;
    └─────────────────────┘
 ```
 
-## Insert data into a distributed table {#inserting-data}
-
 Before we insert the UK price paid data, let's perform a quick experiment to see
 what happens when we insert data into an ordinary table from either host.
 
@@ -622,7 +616,7 @@ CREATE TABLE test.test_table ON CLUSTER cluster_2S_1R
     `id` UInt64,
     `name` String
 )
-ENGINE = ReplicatedMergeTree
+ENGINE = MergeTree()
 ORDER BY id;
 ```
 
@@ -654,16 +648,18 @@ SELECT * FROM test.test_table;
 --   └────┴────────────────────┘
 ```
 
-You will notice that only the row that was inserted into the table on that
+You will notice that unlike with a `ReplicatedMergeTree` table only the row that was inserted into the table on that
 particular host is returned and not both rows.
 
-To read the data from the two shards we need an interface which can handle queries
+To read the data across the two shards, we need an interface which can handle queries
 across all the shards, combining the data from both shards when we run select queries
-on it, and handling the insertion of data to the separate shards when we run insert queries.
+on it or inserting data to both shards when we run insert queries.
 
-In ClickHouse this interface is called a distributed table, which we create using
+In ClickHouse this interface is called a **distributed table**, which we create using
 the [`Distributed`](/engines/table-engines/special/distributed) table engine. Let's take a look at how it works.
 
+## Create a distributed table {#create-distributed-table}
+
 Create a distributed table with the following query:
 
 ```sql
@@ -674,8 +670,12 @@ ENGINE = Distributed('cluster_2S_1R', 'test', 'test_table', rand())
 In this example, the `rand()` function is chosen as the sharding key so that
 inserts are randomly distributed across the shards.
 
-Now query the distributed table from either host and you will get back
-both of the rows which were inserted on the two hosts:
+Now query the distributed table from either host, and you will get back
+both of the rows which were inserted on the two hosts, unlike in our previous example:
+
+```sql
+SELECT * FROM test.test_table_dist;
+```
 
 ```sql
    ┌─id─┬─name───────────────┐
@@ -694,6 +694,8 @@ ON CLUSTER cluster_2S_1R
 ENGINE = Distributed('cluster_2S_1R', 'uk', 'uk_price_paid_local', rand());
 ```
 
+## Insert data into a distributed table {#inserting-data-into-distributed-table}
+
 Now connect to either of the hosts and insert the data:
 
 ```sql