Re: Conflict Detection and Resolution

On Fri, Jul 5, 2024 at 5:12 PM Nisha Moond <nisha(dot)moond412(at)gmail(dot)com> wrote:
>
> Thank you Ajin for reporting the issue, This is now fixed with the
> v4-0003 patch.

Please find v5 patch-set. Changes are:

1) patch003:
Added test cases for all resolvers (034_conflict_resolver.pl).

2) Patch004:
a) Emit error while resolving conflict if conflict resolver is default
'last_update_wins' but track_commit_timetsamp is not enabled.
b) Emit Warning during create and alter subscription when
'detect_conflict' is ON but 'track_commit_timetsamp' is not enabled.
c) Restrict start of pa worker if either max-clock-skew is configured
or conflict detection and resolution is enabled for a subscription.
d) Implement clock-skew delay/error when changes are applied from a
file (apply_spooled_messages).
e) Implement clock-skew delay while applying prepared changes (two
phase txns). The prepare-timestamp to be considered as base for
clock-skew handling as well as for last_update_win resolver.
<TODO: This needs to be analyzed and tested further to see if there is
any side effect of taking prepare-timestamp as base.>

Thanks Ajin fo working on 1.
Thanks Nisha for working on 2a,2b.

thanks
Shveta