Skip to content

Commit 9c30ae7

Browse files
committed
fix typo again after successful test
1 parent d5bba7b commit 9c30ae7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/en/cloud/bestpractices/asyncinserts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ sidebar_label: Asynchronous Inserts
44
title: Asynchronous Inserts (async_insert)
55
---
66

7-
Inseing data into ClickHouse in large batches is a best practice. It saves compute cycles and disk I/O, and therefore it saves money. If your use case allows you to batch your inserts external to ClickHouse, then that is one option. If you would like ClickHouse to create the batches, then you can use the asynchronous INSERT mode described here.
7+
Inserting data into ClickHouse in large batches is a best practice. It saves compute cycles and disk I/O, and therefore it saves money. If your use case allows you to batch your inserts external to ClickHouse, then that is one option. If you would like ClickHouse to create the batches, then you can use the asynchronous INSERT mode described here.
88

99
Use asynchronous inserts as an alternative to both batching data on the client-side and keeping the insert rate at around one insert query per second by enabling the [async_insert](/docs/en/operations/settings/settings.md/#async_insert) setting. This causes ClickHouse to handle the batching on the server-side.
1010

0 commit comments

Comments
 (0)