aadant

Please note that it does not matter if the position is lagging, re-inserting to a replacing merge tree does not matter (few seconds lag is not a big deal)

I am open to discussion but that's a design choice to use RMT. Final is not an issue for this use case, we should document the recommended settings.

@BorisTyshkevich please note that sink != sync.

indeed this config should create table without the `_sign` and with the `is_deleted`. ``` replacingmergetree.delete.column: "is_deleted" ``` @subkanthi : I noticed that the version comparison is not great : as...

Agreed, it does not lose information though. `DateTime64(0)` is also acceptable. ``` python db_load/mysql_parser/mysql_parser.py test2.sql 2023-11-11 21:57:14,279 - root - MainThread - INFO - source = create table t( id...

@subkanthi did you test ``` alter table `leads` drop column `country`; alter table `leads` drop `country`; ``` both should be translated in CH

@Jimerson21 please confirm that it is a similar statement that is not translated.

thanks @Jimerson21 ! > alter table `leads` drop `country` ok that confirms the exact DDL, that should be supported ``` alter table `leads` drop `country` ``` it is equivalent to...

Thank you @subkanthi !

That's on the roadmap. Please note that there is risk of duplicated data. Actually no data should be lost with the RMT. The history is not kept, just like in...