-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
agent.LocalOrchestrator.OnRowsChangesApplied called twice. #1121
Comments
If your scenario, I guess it's called for the state One thing you can do, is to check the values of the argument, something like that: agent.LocalOrchestrator.OnRowsChangesApplied(args =>
{
// check state
if (args.State == SyncRowState.Modified)
Console.WriteLine("State: Insert or Edit rows");
else if (args.State == SyncRowState.Deleted)
Console.WriteLine("State: Delete rows");
else
Console.WriteLine($"State: Retry or Fail ?: {args.State}");
// Check if we have some rows applied
if (args.SyncRows == null || args.SyncRows.Count <= 0)
Console.WriteLine($"No rows applied for this state");
}); If you don't have bulk mode enabled (Only If you need less granular event, you can use
That being said, you still have two events raised, for each state ( Obviously the lesser granular level would be Make sense ? |
That being said, I just made some tests and the interceptor should not be called twice for each rows... |
Another thing to mention, if you are using bulk insert with Then, DMS tries to applies all these rows, one by one. In some cases, applying rows one by row can resolve the issue. Can you check if it's the case for you ? |
I have setup a timer to call synchronise every 3 minutes for the changes that occurs in a table. But my
agent.LocalOrchestrator.OnRowsChangesApplied get called twice for every single change.
What can be the issue?
The text was updated successfully, but these errors were encountered: