Skip to content

Commit d160bc4

Browse files
BlargianBlargian
committed
merge main into branch and resolve merge conflicts
2 parents f6aaf63 + f34438e commit d160bc4

File tree

31 files changed

+918
-282
lines changed

31 files changed

+918
-282
lines changed

‎.github/workflows/pull-request.yaml‎

Lines changed: 30 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@ name: PullRequestCI
33
env:
44
# Force the stdout and stderr streams to be unbuffered
55
PYTHONUNBUFFERED: 1
6-
CI: false
76

87
on: # yamllint disable-line rule:truthy
98
pull_request:
@@ -34,4 +33,33 @@ jobs:
3433
run: yarn install --frozen-lockfile
3534

3635
- name: Build
37-
run: yarn build
36+
id: build
37+
continue-on-error: true
38+
run: |
39+
CI=false DOCUSAURUS_IGNORE_SSG_WARNINGS=true yarn build
40+
echo "exit_code=$?" >> $GITHUB_OUTPUT
41+
42+
- name: Check for validation failures
43+
if: success() || failure() # Run regardless of build success
44+
run: |
45+
FAILED=false
46+
47+
if [ -f ".frontmatter-validation-failed" ]; then
48+
echo "::error::Frontmatter validation failed"
49+
FAILED=true
50+
fi
51+
52+
if [ -f ".floating-pages-validation-failed" ]; then
53+
echo "::error::Floating pages validation failed"
54+
FAILED=true
55+
fi
56+
57+
# Check if build failed with non-validation error
58+
if [ "${{ steps.build.outputs.exit_code }}" != "0" ] && [ "$FAILED" != "true" ]; then
59+
echo "::error::Build failed with exit code ${{ steps.build.outputs.exit_code }}"
60+
exit 1
61+
fi
62+
63+
if [ "$FAILED" = true ]; then
64+
exit 1
65+
fi

‎docs/about-us/support.md‎

Lines changed: 1 addition & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -8,23 +8,10 @@ description: 'Information on ClickHouse Cloud support services'
88

99
# ClickHouse Cloud Support Services
1010

11-
ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our Support Services](https://clickhouse.com/support/program/) page.
11+
ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our ClickHouse Support Program](https://clickhouse.com/support/program/) page.
1212

1313
[Login to the Cloud console](https://console.clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases.
1414

15-
**Service level agreements ("SLA")**
16-
Classification of severity levels for issues reported and response times.
17-
18-
| Severity Level | Trial | Basic | Scale | Enterprise |
19-
|-----------------|-----------------------|--------------------------|----------------------------|----------------------------------------------------------------------------------------|
20-
| Severity 1 | Not available | Not available | 1 hour 24x7 | 30 minute 24x7 |
21-
| Severity 2 | Not available | Not available | 4 business hours | 2 business hours |
22-
| Severity 3 | 1 business day | 1 business day | 1 business day | 1 business day |
23-
24-
(*) Business hours are Monday 00:00 UTC to Saturday 00:00 UTC
25-
26-
Customers can only log Severity 3 tickets for single replica services across tiers. The exception is for a service leveraging the compute-compute separation feature, where the parent service is running 3+ replicas.
27-
2815
You can also subscribe to our [status page](https://status.clickhouse.com) to get notified quickly about any incidents affecting our platform.
2916

3017
:::note

‎docs/cloud/reference/warehouses.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ You can sort services by the warehouse that they belong to.
7575

7676
Because all in a warehouse share the same set of tables, they also share access controls to those other services. This means that all database users that are created in Service 1 will also be able to use Service 2 with the same permissions (grants for tables, views, etc), and vice versa. Users will use another endpoint for each service but will use the same username and password. In other words, _users are shared across services that work with the same storage:_
7777

78-
<Image img={compute_3} size="md" alt="User access across services sharing same data" background='white' />
78+
<Image img={compute_3} size="md" alt="User access across services sharing same data" />
7979

8080
<br />
8181

‎docs/data-modeling/index.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,5 +14,6 @@ This section is about data modeling in ClickHouse and contains the following top
1414
| [Schema Design](/data-modeling/schema-design) | Discusses ClickHouse schema design for optimal performance, considering factors like queries, data updates, latency, and volume. |
1515
| [Dictionary](/dictionary) | An explainer on how to define and use dictionaries to improve query performance and enrich data. |
1616
| [Materialized Views](/materialized-views) | Information on Materialized Views and Refreshable Materialized Views in ClickHouse. |
17+
| [Projections](/data-modeling/projections)| Information on Projections in ClickHouse.|
1718
| [Data Compression](/data-compression/compression-in-clickhouse) | Discusses various compression modes in ClickHouse and how to optimize data storage and query performance by choosing the right compression method for your specific data types and workloads. |
1819
| [Denormalizing Data](/data-modeling/denormalization) | Discusses the denormalization approach used in ClickHouse which aims to improve query performance by storing related data in a single table. |

0 commit comments

Comments
 (0)