search

QuesmaOrg / quesma

Programmable database gateway
https://quesma.com
Other
108 stars 6 forks source link

Add ability to use different engines than `MergeTree` in auto-created ClickHouse tables #934

Open avelanarius opened 3 weeks ago

avelanarius commented 3 weeks ago

Currently, when Quesma auto-creates a table in ClickHouse (on ingest to a new index) it uses the MergeTree engine. This is the correct choice in single-node ClickHouse case or in ClickHouse Cloud case (ClickHouse Cloud automatically replaces it with ReplicatedMergeTree), but for non-cloud multi-node ClickHouse deployments the user might want to use the ReplicatedMergeTree engine 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)

mieciu commented 3 weeks ago

Config-wise this looks like a backend connector property TBH, cc: @pdelewski