You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/cloud/get-started/cloud-quick-start.md
+49-7Lines changed: 49 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,13 +54,18 @@ By default, the scale tier will create 3 replicas each with 4 VCPUs and 16 GiB R
54
54
Users can customize the service resources if required, specifying a minimum and maximum size for replicas to scale between. When ready, select `Create service`.
Congratulations! Your ClickHouse Cloud service is up and running and onboarding is complete. Keep reading for details on how to start ingesting and querying your data.
62
62
63
63
## 2. Connect to ClickHouse
64
+
There are 2 ways to connect to ClickHouse:
65
+
- Connect using our web-based SQL console
66
+
- Connect with your app
67
+
68
+
### Connect using SQL console
64
69
65
70
For getting started quickly, ClickHouse provides a web-based SQL console to which you will be redirected on completing onboarding.
66
71
@@ -87,7 +92,43 @@ You should see 4 databases in the list, plus any that you may have added.
87
92
88
93
That's it - you are ready to start using your new ClickHouse service!
89
94
90
-
## 3. Create a database and table
95
+
### Connect with your app
96
+
97
+
Press the connect button from the navigation menu. A modal will open offering the credentials to your service and offering you a set of instructions on how to connect with your interface or language clients.
If you can’t see your language client, you may want to check our list of [Integrations](https://clickhouse.com/docs/en/integrations).
105
+
106
+
## 3. Add data
107
+
108
+
ClickHouse is better with data! There are multiple ways to add data and most of them are available on the Data Sources page, which can be accessed in the navigation menu.
- Setup a ClickPipe to start ingesting data from data sources like S3, Postgres, Kafka, GCS
117
+
- Use the SQL console
118
+
- Use the ClickHouse client
119
+
- Upload a file - accepted formats include JSON, CSV and TSV
120
+
- Upload data from file URL
121
+
122
+
### ClickPipes
123
+
124
+
[ClickPipes](http://clickhouse.com/docs/en/integrations/clickpipes) is a managed integration platform that makes ingesting data from a diverse set of sources as simple as clicking a few buttons. Designed for the most demanding workloads, ClickPipes's robust and scalable architecture ensures consistent performance and reliability. ClickPipes can be used for long-term streaming needs or one-time data loading job.
125
+
126
+
<divclass="eighty-percent">
127
+

128
+
</div>
129
+
<br/>
130
+
131
+
### Add data using the SQL Console
91
132
92
133
Like most database management systems, ClickHouse logically groups tables into **databases**. Use the [`CREATE DATABASE`](../../sql-reference/statements/create/database.md) command to create a new database in ClickHouse:
93
134
@@ -125,7 +166,7 @@ Table engines determine:
125
166
There are many table engines to choose from, but for a simple table on a single-node ClickHouse server, [`MergeTree`](/en/engines/table-engines/mergetree-family/mergetree.md) is your likely choice.
126
167
:::
127
168
128
-
###3a. A Brief Intro to Primary Keys
169
+
####A Brief Intro to Primary Keys
129
170
130
171
Before you go any further, it is important to understand how primary keys work in ClickHouse (the implementation
131
172
of primary keys might seem unexpected!):
@@ -147,6 +188,9 @@ For a deep dive into core ClickHouse concepts, see ["Core Concepts"](../../manag
147
188
148
189
## 4. Insert Data
149
190
191
+
#### Insert data into your table
192
+
193
+
150
194
You can use the familiar [`INSERT INTO TABLE`](../../sql-reference/statements/insert-into.md) command with ClickHouse, but it is important to understand that each insert into a [`MergeTree`](/en/engines/table-engines/mergetree-family/mergetree.md) table causes a **part** to be created in storage.
151
195
152
196
:::tip ClickHouse best practice
@@ -176,9 +220,7 @@ Let's verify it worked:
176
220
SELECT*FROMhelloworld.my_first_table
177
221
```
178
222
179
-
You should see the four rows of data that were inserted:
180
-
181
-
## 5. Using the ClickHouse Client
223
+
### Add data using the ClickHouse Client
182
224
183
225
You can also connect to your ClickHouse Cloud service using a command-line tool named [**clickhouse client**](/docs/en/interfaces/cli). Click `Connect` on the left menu to access these details. From the dialog select `Native` from the drop-down:
Copy file name to clipboardExpand all lines: docs/en/cloud/manage/jan2025_faq/summary.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ We are introducing new features to optimize the sizing and cost-efficiency of Cl
15
15
16
16
We are adding a new Enterprise tier to serve the needs of the most demanding customers and workloads, with focus on industry-specific security and compliance features, even more controls over underlying hardware and upgrades, and advanced disaster recovery features.
17
17
18
-
You can read about these and other functional changes in this [blog][LINK - TO ADD].
18
+
You can read about these and other functional changes in this [blog][https://clickhouse.com/blog/evolution-of-clickhouse-cloud-new-features-superior-performance-tailored-offerings].
Copy file name to clipboardExpand all lines: docs/en/cloud/reference/changelog.md
+75Lines changed: 75 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,81 @@ title: Cloud Changelog
6
6
7
7
In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/docs/en/cloud/reference/cloud-compatibility.md) page.
8
8
9
+
## January 23, 2024
10
+
11
+
### Changes to ClickHouse Cloud tiers
12
+
13
+
We are dedicated to adapting our products to meet the ever-changing requirements of our customers. Since its introduction in GA over the past two years, ClickHouse Cloud has evolved substantially, and we've gained invaluable insights into how our customers leverage our cloud offerings.
14
+
15
+
We are introducing new features to optimize the sizing and cost-efficiency of ClickHouse Cloud services for your workloads. These include **compute-compute separation**, high-performance machine types, and **single-replica services**. We are also evolving automatic scaling and managed upgrades to execute in a more seamless and reactive fashion.
16
+
17
+
We are adding a **new Enterprise tier** to serve the needs of the most demanding customers and workloads, with focus on industry-specific security and compliance features, even more controls over underlying hardware and upgrades, and advanced disaster recovery features.
18
+
19
+
To support these changes, we are restructuring our current **Development** and **Production** tiers to more closely match how our evolving customer base is using our offerings. We are introducing the **Basic** tier, oriented toward users that are testing out new ideas and projects, and the **Scale** tier, matching users working with production workloads and data at scale.
20
+
21
+
You can read about these and other functional changes in this [blog](https://clickhouse.com/blog/evolution-of-clickhouse-cloud-new-features-superior-performance-tailored-offerings). Existing customers will need to take action to select a [new plan](https://clickhouse.com/pricing). Customer-facing communication was sent via email to organization administrators, and the following [FAQ](https://clickhouse.com/docs/en/cloud/manage/jan-2025-faq/summary) covers the key changes and timelines.
22
+
23
+
### Warehouses: Compute-compute separation (GA)
24
+
25
+
Compute-compute separation (also known as "Warehouses") is Generally Available; please refer to [blog](https://clickhouse.com/blog/introducing-warehouses-compute-compute-separation-in-clickhouse-cloud) for more details and the [documentation](https://clickhouse.com/docs/en/cloud/reference/warehouses).
26
+
27
+
### Single-replica services
28
+
29
+
We are introducing the concept of a "single-replica service", both as a standalone offering and within warehouses. As a standalone offering, single-replica services are size limited and intended to be used for small test workloads. Within warehouses, single-replica services can be deployed at larger sizes, and utilized for workloads not requiring high availability at scale, such as restartable ETL jobs.
30
+
31
+
### Vertical auto-scaling improvements
32
+
33
+
We are introducing a new vertical scaling mechanism for compute replicas, which we call "Make Before Break" (MBB). This approach adds one or more replicas of the new size before removing the old replicas, preventing any loss of capacity during scaling operations. By eliminating the gap between removing existing replicas and adding new ones, MBB creates a more seamless and less disruptive scaling process. It is especially beneficial in scale-up scenarios, where high resource utilization triggers the need for additional capacity, since removing replicas prematurely would only exacerbate the resource constraints.
34
+
35
+
### Horizontal scaling (GA)
36
+
37
+
Horizontal scaling is now Generally Available. Users can add additional replicas to scale out their service through the APIs and the cloud console. Please refer to the [documentation](https://clickhouse.com/docs/en/manage/scaling#self-serve-horizontal-scaling) for information.
38
+
39
+
### Configurable backups
40
+
41
+
We now support the ability for customers to export backups to their own cloud account; please refer to the [documentation](https://clickhouse.com/docs/en/cloud/manage/backups#configurable-backups) for additional information.
42
+
43
+
### Managed upgrade improvements
44
+
45
+
Safe managed upgrades deliver significant value to our users by allowing them to stay current with the database as it moves forward to add features. With this rollout, we applied the "make before break" (or MBB) approach to upgrades, further reducing impact to running workloads.
46
+
47
+
### HIPAA support
48
+
49
+
We now support HIPAA in compliant regions, including AWS `us-east-1`, `us-west-2` and GCP `us-central1`, `us-east1`. Customers wishing to onboard must sign a Business Associate Agreement (BAA) and deploy to the compliant version of the region. For more information on HIPAA, please refer to the [documentation](https://clickhouse.com/docs/en/cloud/security/security-and-compliance).
50
+
51
+
### Scheduled upgrades
52
+
53
+
Users can schedule upgrades for their services. This feature is supported for Enterprise tier services only. For more information on Scheduled upgrades, please refer to the [documentation](https://clickhouse.com/docs/en/manage/updates).
54
+
55
+
### Language client support for complex types
56
+
57
+
[Golang](https://github.com/ClickHouse/clickhouse-go/releases/tag/v2.30.1), [Python](https://github.com/ClickHouse/clickhouse-connect/releases/tag/v0.8.11), and [NodeJS](https://github.com/ClickHouse/clickhouse-js/releases/tag/1.10.1) clients added support for Dynamic, Variant, and JSON types.
58
+
59
+
### DBT support for Refreshable Materialized Views
60
+
61
+
DBT now [supports Refreshable Materialized Views](https://github.com/ClickHouse/dbt-clickhouse/releases/tag/v1.8.7) in the `1.8.7` release.
62
+
63
+
### JWT token support
64
+
65
+
Support has been added for JWT-based authentication in the JDBC driver v2, clickhouse-java, [Python](https://github.com/ClickHouse/clickhouse-connect/releases/tag/v0.8.12), and[ NodeJS](https://github.com/ClickHouse/clickhouse-js/releases/tag/1.10.0) clients.
66
+
67
+
JDBC / Java will be in[ 0.8.0](https://github.com/ClickHouse/clickhouse-java/releases/tag/v0.8.0) when it's released - ETA pending.
68
+
69
+
### Prometheus integration improvements
70
+
71
+
We've added several enhancements for the Promethous integration:
72
+
73
+
-**Organization-level endpoint**. We've introduced an enhancement to our Prometheus integration for ClickHouse Cloud. In addition to service-level metrics, the API now includes an endpoint for **organization-level metrics**. This new endpoint automatically collects metrics for all services within your organization, streamlining the process of exporting metrics into your Prometheus collector. These metrics can be integrated with visualization tools like Grafana and Datadog for a more comprehensive view of your organization's performance.
74
+
75
+
This feature is available now for all users. You can find more details [here](https://clickhouse.com/docs/en/integrations/prometheus).
76
+
77
+
-**Filtered metrics**. We've added support for returning a filtered list of metrics in our Prometheus integration for ClickHouse Cloud. This feature helps reduce response payload size by enabling you to focus on metrics that are critical for monitoring the health of your service.
78
+
79
+
This functionality is available via an optional query parameter in the API, making it easier to optimize your data collection and streamline integrations with tools like Grafana and Datadog.
80
+
81
+
The filtered metrics feature is now available for all users. You can find more details [here](https://clickhouse.com/docs/en/integrations/prometheus).
0 commit comments