From 78cbce75dd43aacceb487f68618ab0f5aa5d92ed Mon Sep 17 00:00:00 2001 From: Piotr Grabowski Date: Thu, 31 Oct 2024 15:52:23 +0100 Subject: [PATCH] Add "ClickHouse engine" limitation Currently Quesma auto-creates tables with `MergeTree` engine. It's automatically converted to `ReplicatedMergeTree` in case of ClickHouse cloud, but not in case of a local multi-node cluster and the user can't control it. Refs #934 Signed-off-by: Piotr Grabowski --- docs/public/docs/limitations.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/public/docs/limitations.md b/docs/public/docs/limitations.md index f4e32cd9e..c3bd45cb5 100644 --- a/docs/public/docs/limitations.md +++ b/docs/public/docs/limitations.md @@ -14,9 +14,14 @@ Quesma has been tested with the following software versions: | Docker | `24.0.7` | | Elasticsearch/Kibana | `8.11.1` | | ClickHouse | `24.1`, `23.12` | +| ClickHouse Cloud | `24.5` | | OpenSearch/OpenSearch Dashboards | `2.12.0` | | Hydrolix | `v4.8.12` | +### ClickHouse limitations +* When using a cluster deployment of ClickHouse, the tables automatically created by Quesma (during [Ingest](/ingest.md)) will use the `MergeTree` engine. If you wish to use the `ReplicatedMergeTree` engine instead, you will have to create the tables manually with `ReplicatedMergeTree` engine before ingesting data to Quesma. + * *Note: On ClickHouse Cloud, the tables automatically created by Quesma will use the `ReplicatedMergeTree` engine (ClickHouse Cloud default engine).* + ## Functional limitations Currently supported: - front-end support for Kibana and Open Search Dashboards, limited to Discover(LogExplorer) interface and Dashboard panels