Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ Many real-world workloads involve repeated queries against the same or almost th
ClickHouse provides various optimization techniques to optimize for such query patterns.
One possibility is to tune the physical data layout using index structures (e.g., primary key indexes, skipping indexes, projections) or pre-calculation (materialized views).
Another possibility is to use ClickHouse's [query cache](/core/concepts/features/performance/caches/query-cache) to avoid repeated query evaluation.
The downside of the first approach is that that it requires manual intervention and monitoring by a database administrator.
The downside of the first approach is that it requires manual intervention and monitoring by a database administrator.
The second approach may return stale results (as the query cache is transactionally not consistent) which may or may not be acceptable, depending on the use case.

The query condition cache provides an elegant solution for both problems.
Expand Down
2 changes: 1 addition & 1 deletion core/get-started/quickstarts/tutorial.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -493,7 +493,7 @@ Write some queries that join the `taxi_zone_dictionary` with your `trips` table.
Notice the output of the above `JOIN` query is the same as the query before it that used `dictGetOrDefault` (except that the `Unknown` values aren't included). Behind the scenes, ClickHouse is actually calling the `dictGet` function for the `taxi_zone_dictionary` dictionary, but the `JOIN` syntax is more familiar for SQL developers.
</Note>

2. This query returns rows for the the 1000 trips with the highest tip amount, then performs an inner join of each row with the dictionary:
2. This query returns rows for the 1000 trips with the highest tip amount, then performs an inner join of each row with the dictionary:
```sql
SELECT *
FROM trips
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -494,7 +494,7 @@ ClickHouse vector indexes supports the following quantization options:
Quantization reduces the precision of vector searches compared to searching the original full-precision floating-point values (`f32`).
However, on most datasets, half-precision brain float quantization (`bf16`) results in a negligible precision loss, therefore vector similarity indexes use this quantization technique by default.
Quarter precision (`i8`) and binary (`b1`) quantization causes appreciable precision loss in vector searches.
We recommend both quantizations only if the the size of the vector similarity index is significantly larger than the available DRAM size.
We recommend both quantizations only if the size of the vector similarity index is significantly larger than the available DRAM size.
In this case, we also suggest enabling rescoring ([vector_search_index_fetch_multiplier](/core/reference/settings/session-settings#vector_search_index_fetch_multiplier), [vector_search_with_rescoring](/core/reference/settings/session-settings#vector_search_with_rescoring)) to improve accuracy.
Binary quantization is only recommended for 1) normalized embeddings (i.e. vector length = 1, OpenAI models are usually normalized), and 2) if the cosine distance is used as distance function.
Binary quantization internally uses the Hamming distance to construct and search the proximity graph.
Expand Down
4 changes: 2 additions & 2 deletions core/reference/functions/regular-functions/url-functions.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1482,7 +1482,7 @@ SELECT queryStringAndFragment('https://clickhouse.com/docs?query=value&param=123

Introduced in: v1.1.0

Extracts the the top-level domain from a URL.
Extracts the top-level domain from a URL.

<Note>
The URL can be specified with or without a protocol.
Expand Down Expand Up @@ -1528,7 +1528,7 @@ SELECT topLevelDomain('svn+ssh://www.some.svn-hosting.com:80/repo/trunk');

Introduced in: v22.10.0

Extracts the the top-level domain from a URL.
Extracts the top-level domain from a URL.
Similar to [`topLevelDomain`](#topLevelDomain), but conforms to [RFC 3986](https://datatracker.ietf.org/doc/html/rfc3986).


Expand Down
2 changes: 1 addition & 1 deletion core/reference/functions/table-functions/fuzzJSON.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ fuzzJSON({ named_collection [, option=value [,..]] | json_str[, random_seed] })

## Returned value {#returned_value}

A table object with a a single column containing perturbed JSON strings.
A table object with a single column containing perturbed JSON strings.

## Usage Example {#usage-example}

Expand Down
2 changes: 1 addition & 1 deletion core/reference/functions/table-functions/postgresql.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,6 @@ CREATE TABLE pg_table_schema_with_dots (a UInt32)
- [The PostgreSQL table engine](/core/reference/engines/table-engines/integrations/postgresql)
- [Using PostgreSQL as a dictionary source](/core/reference/statements/create/dictionary/sources/postgresql)

### Replicating or migrating Postgres data with with PeerDB {#replicating-or-migrating-postgres-data-with-with-peerdb}
### Replicating or migrating Postgres data with PeerDB {#replicating-or-migrating-postgres-data-with-peerdb}

> In addition to table functions, you can always use [PeerDB](https://docs.peerdb.io/introduction) by ClickHouse to set up a continuous data pipeline from Postgres to ClickHouse. PeerDB is a tool designed specifically to replicate data from Postgres to ClickHouse using change data capture (CDC).
2 changes: 1 addition & 1 deletion core/reference/settings/merge-tree-settings.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -1205,7 +1205,7 @@ new nodes.
<SettingsInfoBlock type="UInt64" default_value="1000" />

How many records may be in the ClickHouse Keeper log if there is inactive
replica. An inactive replica becomes lost when when this number exceed.
replica. An inactive replica becomes lost when this number exceed.

Possible values:
- Any positive integer.
Expand Down
2 changes: 1 addition & 1 deletion core/reference/system-tables/events.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4729,7 +4729,7 @@ Number of times a text index posting list has been found in the cache.

### TextIndexPostingsCacheMisses {#textindexpostingscachemisses}

Number of times a a text index posting list has not been found in the cache.
Number of times a text index posting list has not been found in the cache.

### TextIndexReadDictionaryBlocks {#textindexreaddictionaryblocks}

Expand Down
2 changes: 1 addition & 1 deletion integrations/connectors/tools/pg_clickhouse/reference.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -681,7 +681,7 @@ LOAD
```

It's not normally necessary to use [LOAD], as Postgres will automatically load
pg_clickhouse the first time any of of its features (functions, foreign
pg_clickhouse the first time any of its features (functions, foreign
tables, etc.) are used.

The one time it may be useful to [LOAD] pg_clickhouse is to [SET](#set)
Expand Down
2 changes: 1 addition & 1 deletion integrations/connectors/tools/pg_clickhouse/tutorial.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -620,7 +620,7 @@ table.
Time: 2.012 ms
```

2. This query returns rows for the the 1000 trips with the highest tip
2. This query returns rows for the 1000 trips with the highest tip
amount, then performs an inner join of each row with the dictionary:

```sql
Expand Down
4 changes: 2 additions & 2 deletions products/clickstack/deployment/managed.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ From the ClickHouse Cloud landing page, select `New service` to create a new ser
<Step>
### Setup ingestion {#setup-ingestion-create-new}

Once your service has been provisioned, ensure the the service is selected and click "ClickStack" from the left menu.
Once your service has been provisioned, ensure the service is selected and click "ClickStack" from the left menu.

<SetupManagedIngestion/>
</Step>
Expand Down Expand Up @@ -121,7 +121,7 @@ If auto detection is successful, you should be directed to the search view where

<Image img="/images/clickstack/getting-started/clickstack_managed_ui.png" size="lg" alt='ClickStack UI'/>

If this step is successful, that that's it — you’re all set 🎉, otherwise proceed to setting up ingestion.
If this step is successful, that's it — you’re all set 🎉, otherwise proceed to setting up ingestion.
</Step>
<Step>
### Setup ingestion {#setup-ingestion-existing-service}
Expand Down
2 changes: 1 addition & 1 deletion products/clickstack/getting-started/managed.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ To create a Managed ClickStack service in [ClickHouse Cloud](https://console.cli
<Step>
## Setup ingestion {#setup-ingestion}

Once your service has been provisioned, ensure the the service is selected and click "ClickStack" from the left menu.
Once your service has been provisioned, ensure the service is selected and click "ClickStack" from the left menu.

<SetupManagedIngestion/>
</Step>
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -309,7 +309,7 @@ the label `comp-parallel-replicas`.
You can check what settings are being used for each query in the
[`system.query_log`](/core/reference/system-tables/query_log) table. You can
also look at the [`system.events`](/core/reference/system-tables/events)
table to see all the events that have occured on the server, and you can use the
table to see all the events that have occurred on the server, and you can use the
[`clusterAllReplicas`](/core/reference/functions/table-functions/cluster) table function to see the tables on all the replicas
(if you're a cloud user, use `default`).

Expand Down
6 changes: 3 additions & 3 deletions products/cloud/reference/billing/marketplace/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,8 @@ This section details billing related topics for Marketplace.
|---------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [Marketplace Billing](/products/cloud/reference/billing/marketplace/overview) | FAQ on Marketplace billing. |
| [AWS Marketplace PAYG](/products/cloud/reference/billing/marketplace/aws-marketplace-payg) | Get started with ClickHouse Cloud on the AWS Marketplace via a PAYG (Pay-as-you-go) Public Offer. |
| [AWS Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/aws-marketplace-committed) | Get started with ClickHouse Cloud on the AWS Marketplace via a committed contract. A committed contract, also known as a a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |
| [AWS Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/aws-marketplace-committed) | Get started with ClickHouse Cloud on the AWS Marketplace via a committed contract. A committed contract, also known as a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |
| [GCP Marketplace PAYG](/products/cloud/reference/billing/marketplace/gcp-marketplace-payg) | Get started with ClickHouse Cloud on the GCP Marketplace via a PAYG (Pay-as-you-go) Public Offer. |
| [GCP Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/gcp-marketplace-committed) | Get started with ClickHouse Cloud on the GCP Marketplace via a committed contract. A committed contract, also known as a a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |
| [GCP Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/gcp-marketplace-committed) | Get started with ClickHouse Cloud on the GCP Marketplace via a committed contract. A committed contract, also known as a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |
| [Azure Marketplace PAYG](/products/cloud/reference/billing/marketplace/azure-marketplace-payg) | Get started with ClickHouse Cloud on the Azure Marketplace via a PAYG (Pay-as-you-go) Public Offer. |
| [Azure Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/azure-marketplace-committed) | Get started with ClickHouse Cloud on the Azure Marketplace via a committed contract. A committed contract, also known as a a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |
| [Azure Marketplace Committed Contract](/products/cloud/reference/billing/marketplace/azure-marketplace-committed) | Get started with ClickHouse Cloud on the Azure Marketplace via a committed contract. A committed contract, also known as a Private Offer, allows customers to commit to spending a certain amount on ClickHouse Cloud over a period of time. |