Skip to content

Commit 577a8e7

Browse files
authored
Merge pull request #3982 from Blargian/changelog_june27
Change log: update cloud change log for June 27
2 parents 3841f30 + f9f10a1 commit 577a8e7

File tree

2 files changed

+17
-6
lines changed

2 files changed

+17
-6
lines changed

docs/cloud/reference/changelog.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,10 +30,21 @@ import query_endpoints from '@site/static/images/cloud/reference/may-17-query-en
3030
import dashboards from '@site/static/images/cloud/reference/may-30-dashboards.png';
3131

3232
In addition to this ClickHouse Cloud changelog, please see the [Cloud Compatibility](/cloud/reference/cloud-compatibility.md) page.
33-
## June 13, 2025 {#june-13-2025}
3433

35-
- We're excited to announce that ClickHouse Cloud Dashboards are now generally available. Dashboards allow users to visualize queries on dashboards, interact with data via filters and query parameters, and manage sharing.
34+
## June 27, 2025 {#june-27-2025}
35+
36+
- We now officially support a Terraform provider for managing database privileges
37+
which is also compatible with self-managed deployments. Please refer to the
38+
[blog](https://clickhouse.com/blog/new-terraform-provider-manage-clickhouse-database-users-roles-and-privileges-with-code)
39+
and our [docs](https://registry.terraform.io/providers/ClickHouse/clickhousedbops/latest/docs)
40+
for more information.
41+
- Enterprise tier services can now enlist in the [slow release channel](/manage/updates/#slow-release-channel-deferred-upgrades) to defer
42+
upgrades by two weeks after the regular release to permit additional time for
43+
testing.
44+
45+
## June 13, 2025 {#june-13-2025}
3646

47+
- We're excited to announce that ClickHouse Cloud Dashboards are now generally available. Dashboards allow users to visualize queries on dashboards, interact with data via filters and query parameters, and manage sharing.
3748
- API key IP filters: we are introducing an additional layer of protection for your interactions with ClickHouse Cloud. When generating an API key, you may setup an IP allow list to limit where the API key may be used. Please refer to the [documentation](https://clickhouse.com/docs/cloud/security/setting-ip-filters) for details.
3849

3950
## May 30, 2025 {#may-30-2025}

docs/integrations/data-ingestion/google-dataflow/templates/bigquery-to-clickhouse.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ The template can read the entire table or filter specific records using a provid
5858
Default values for all `ClickHouseIO` parameters can be found in [`ClickHouseIO` Apache Beam Connector](/integrations/apache-beam#clickhouseiowrite-parameters)
5959
:::
6060

61-
## Source and Target Tables Schema {#source-and-target-tables-schema}
61+
## Source and target tables schema {#source-and-target-tables-schema}
6262

6363
To effectively load the BigQuery dataset into ClickHouse, the pipeline performs a column inference process with the following phases:
6464

@@ -147,14 +147,14 @@ gcloud dataflow flex-template run "bigquery-clickhouse-dataflow-$(date +%Y%m%d-%
147147
--parameters inputTableSpec="<bigquery table id>",jdbcUrl="jdbc:clickhouse://<clickhouse host>:<clickhouse port>/<schema>?ssl=true&sslmode=NONE",clickHouseUsername="<username>",clickHousePassword="<password>",clickHouseTable="<clickhouse target table>"
148148
```
149149

150-
### Command Breakdown {#command-breakdown}
150+
### Command breakdown {#command-breakdown}
151151

152152
- **Job Name:** The text following the `run` keyword is the unique job name.
153153
- **Template File:** The JSON file specified by `--template-file-gcs-location` defines the template structure and
154154
details about the accepted parameters. The mention file path is public and ready to use.
155155
- **Parameters:** Parameters are separated by commas. For string-based parameters, enclose the values in double quotes.
156156

157-
### Expected Response {#expected-response}
157+
### Expected response {#expected-response}
158158

159159
After running the command, you should see a response similar to the following:
160160

@@ -188,6 +188,6 @@ This error occurs when ClickHouse runs out of memory while processing large batc
188188
* Increase the instance resources: Upgrade your ClickHouse server to a larger instance with more memory to handle the data processing load.
189189
* Decrease the batch size: Adjust the batch size in your Dataflow job configuration to send smaller chunks of data to ClickHouse, reducing memory consumption per batch. These changes can help balance resource usage during data ingestion.
190190

191-
## Template Source Code {#template-source-code}
191+
## Template source code {#template-source-code}
192192

193193
The template's source code is available in ClickHouse's [DataflowTemplates](https://github.com/ClickHouse/DataflowTemplates) fork.

0 commit comments

Comments
 (0)