Skip to content

Commit 7ab9856

Browse files
committedMar 14, 2025·
make linter happy
1 parent eba1435 commit 7ab9856

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed
 

‎docs/use-cases/time-series/query-performance.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ keywords: [time-series]
1313

1414

1515
Before attempting other optimizations, users should optimize their ordering key to ensure ClickHouse produces the fastest possible results.
16-
Choosing the key right largely depends on the queries you’re going to run. Suppose most of our queries filter by project and subproject columns.
16+
Choosing the key right largely depends on the queries you’re going to run. Suppose most of our queries filter by `project` and `subproject` columns.
1717
In this case, its a good idea to add them to the ordering key - as well as the time column since we query on time as well:
1818

1919
Let's create another version of the table that has the same column types as `wikistat`, but is ordered by `(project, subproject, time)`.

‎docs/use-cases/time-series/storage-efficiency.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ This section demonstrates practical techniques to reduce storage requirements wh
1414
## Type optimization
1515

1616
The general approach to optimizing storage efficiency is using optimal data types.
17-
Let’s take the project and subprojects columns. These columns are of type String, but have a relatively small amount of unique values:
17+
Let’s take the `project` and `subproject` columns. These columns are of type String, but have a relatively small amount of unique values:
1818

1919
```sql
2020
SELECT

0 commit comments

Comments
 (0)