-
Bug
-
Resolution: Done
-
Major
-
1.2.0.Final
-
None
This Bug is the same as DBZ-1152
Sometimes during update of multiple primary keys order of change_lsn is not monotonic.
Basically, fix for above issue works only for one record with ChangePosition equal to commited offset
It seems, that event_serial_no should be calculated on common start_lsn not only on records with duplicated change_lsns
I will create PR with tests to reproduce
Also I have a solution in mind which does not require changes in implementation of event_serial_no