aadant

@subkanthi i am surprised you managed to replicate the DateTime, can you check if the now() return the same rough time. this is important for the repro : ``` environment:...

Please note that this bug is not fixed for DateTime(4), DateTime(5) and DateTime(6) in version 2.6.0. see https://github.com/Altinity/clickhouse-sink-connector/issues/1056

Regarding the results, you are querying a RMT so you should use FINAL or settings final=1

@subkanthi ^ see

You can also use tables per connector and modify the view to union all the status.

@Bens-ct you can use something like that if you have multiple connectors ``` CREATE OR REPLACE VIEW altinity_sink_connector.show_replica_status ( `seconds_behind_source` Int32, `duration_behind_source` String, `utc_time` DateTime('UTC'), `local_time` DateTime, `id` String, `offset_key`...

@wgtmac the pluggable tokenizer is indeed a valid concern but this type of filter is used for alpha-numeric tokens separated by space mostly machine generated.

this one is language independent @wgtmac

@meysammeisam indeed, it is a cool feature. We would also need to implement the checksum for Postgres and the fast table counts. This project is open source, feel free to...

@subkanthi any idea ? this should work ... @kamil-bednarek can you post the table structure ? the best way to initialize from MySQL is to use `mysql_dumper.py` / `clickhouse_loader.py` from...