You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have finished some features on this,but thier just on on private branch, I want to hear more request and advice from anyone.
1. support checkpoint on table initial load.
1. require Mysql and have sorted primary key.
2. support update event.
1. just translate UPDATE event to INSERT, it's friendly for `ReplacingMergeTree`.
2. using `final` ON `SELECT`.
3. planing to support DELETE event.
1. just translate DELETE Event to INSERT(always using soft delete).
2. require dst clickhouse table has `deleted_at` field.
3. and also increment `version key`, currently just support `DateTime` field.
4. Batch Insert
as well as we know, clickhouse-mysql process each binlog one by one using single insert mode, it's very slow. the feature allow caching binlog event and batch insert.
The text was updated successfully, but these errors were encountered:
Thanks a lot! All these changes looks very interesting!
Can you, please, elaborate a little items 1 and 4, to clarify what exactly you propose.
Items 2 and 3 seems to be more/less clear.
Let's talk over all these changes and make plan on how to proceed.
hi,team:
I have finished some features on this,but thier just on on private branch, I want to hear more request and advice from anyone.
1. support checkpoint on table initial load.
2. support update event.
3. planing to support DELETE event.
4. Batch Insert
as well as we know, clickhouse-mysql process each binlog one by one using single insert mode, it's very slow. the feature allow caching binlog event and batch insert.
The text was updated successfully, but these errors were encountered: