I’m not sure how far this will go, but figured I’d ask here.
To give context, we are using AWS DMS to replicate CDC binlog records to S3 from an Aurora MySQL instance. However due to binlog precision only being to the second we opted to add an additional column to all tables that auto-updates with a millisecond precision timestamp.
We have several very large tables that can only be modified by pt-online-schema-change. However, when executing this command our AWS DMS replication server complains that the schema of the table no longer matches (column count with new column) the incoming CDC records and simply skips replication entirely.
I’m curious if anyone has seen this issue before, as normal ALTER commands function fine.