Add ability to use different engines than MergeTree in auto-created ClickHouse tables
#934
Comments
avelanarius
added a commit
that referenced
this issue
Oct 31, 2024
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 <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 31, 2024
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. If the user has a local multi-node cluster, the tables automatically created by Quesma won't be replicated - the only solution is to create them manually with the correct `ReplicatedMergeTree` engine. Refs #934 Signed-off-by: Piotr Grabowski <[email protected]>
|
Config-wise this looks like a backend connector property TBH, cc: @pdelewski |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when Quesma auto-creates a table in ClickHouse (on ingest to a new index) it uses the
MergeTreeengine. This is the correct choice in single-node ClickHouse case or in ClickHouse Cloud case (ClickHouse Cloud automatically replaces it withReplicatedMergeTree), but for non-cloud multi-node ClickHouse deployments the user might want to use theReplicatedMergeTreeengine instead. Without an easy way to customize this behavior, the only workaround is to manually create (recreate) the table with the desired engine.(this shortcoming was encountered by a user)
The text was updated successfully, but these errors were encountered: