ClickHouse/tests/integration/test_materialized_mysql_database
Haavard Kvaalen c41923c595 MaterializedMySQL: Update GTID set at end of transaction
We would update the set of seen GTIDs as soon as we saw a GTID_EVENT,
which arrives before a transaction.  This would mostly work fine, but
if we lost the connection to MySQL in the middle of a large transaction
we would persist that the transaction had been processed as soon as the
transaction had started.  When the connection was reestablished, we
would not process the transaction again, which meant that we only
applied parts of it.

Fix this by updating the seen GTIDs at the end of the transaction
instead.
2021-10-07 14:09:00 +02:00
..
configs Change <yandex> to <clickhouse> in configs 2021-09-20 01:38:53 +03:00
__init__.py rename MaterializeMySQL to MaterializedMySQL 2021-07-26 21:17:28 +03:00
materialize_with_ddl.py MaterializedMySQL: Update GTID set at end of transaction 2021-10-07 14:09:00 +02:00
test.py MaterializedMySQL: Update GTID set at end of transaction 2021-10-07 14:09:00 +02:00