aadant

I think the idea is to only backup the partitions that we are actively written to, for example the ones that are on hot storage. or just one partition at...

@BorisTyshkevich the current system with RMT and final allows for exactly once semantics. It already works fine.

yes this is a known edge case for debezium and MySQL. here is a workaround. https://stackoverflow.com/questions/57443976/debezium-does-not-capture-cascade-delete

@AdamKatzDev it would be a custom solution on your end.

confirmed here https://code.openark.org/blog/mysql/things-that-dont-work-well-with-mysqls-foreign-key-implementation#more-8226

Cool, will try out. If it works, we should add it to the default config (even commented)

JSON is now addressed https://github.com/Altinity/clickhouse-sink-connector/pull/316

Currently only the RMT is the only supported engine. We may support MergeTree for history tables. But that's an enhancement.

@AjinkyaTaranekar, it should be possible to use RRMT (ReplicatedReplacingMergeTree) as default engine. @subkanthi is it something you tested ? What would be the setting to get it working ?

@AjinkyaTaranekar writing to a distributed table is slower than a regular MergeTree but this enables to shard the data. I think a CH node is typically quicker than a MySQL...