Map comparator event raised when the input map copy is completed.

Map comparator event raised when the input map copy starts.

Map comparator event raised when the updates to the final result map(s) have completed.

Map comparator event raised when the updates to the final result map(s) have started.

Map comparator event raised when the scan for the topics referenced (directly or indirectly) from the input map has completed.

Map comparator event raised when the scan for the topics referenced (directly or indirectly) from the input map has started.

Raised when topic alignment process completed.

Provides alignment information on referenced topics, giving an indication of the number of comparisons to be performed - the size of the alignedTopics Dictionary.

Map comparator event raised when topic alignment process started.

Map comparator event raised when each topic comparison stage has been completed.

Map comparator heartbeat event raised when inside the compare stage. Progress on the 'Main comparator' stage is monitored by a heartbeat. This callback event is best used to report when the comparator was last known to be alive.

1. Will be called at most once a second.
2. Not receiving this event should not be interpreted as the comparison stopping or being broken, but usually a sign that the comparison is busy processing.
3. This runs on the same thread as the comparison, so the code you add here will increase the comparison time.

Map comparator event raised when each topic comparison stage has been started.

Map comparator event raised when the processing of a topic has completed.

Map comparator event raised when a failure happens during the processing of a topic.

Map comparator event raised when the processing of a topic has started.

Map comparator event raised before a topic compare to return the total number of topic comparison stages that are involved

Topic comparator event raised when each stage completes.

Topic comparator heartbeat event raised when inside the compare stage. Progress on the 'Main comparator' stage is monitored by a heartbeat. This event is best used to report when the comparator was last known to be alive.

Notes:

1. Will be called at most once a second.
2. Not receiving this event should not be interpreted as the comparison stopping or being broken, but usually a sign that the comparison is busy processing.
3. This runs on the same thread as the comparison, so the code you add here will increase the comparison time.

Topic comparator event raised on computing the total for the number of stages required for the comparison.

Topic comparator event raised when each stage starts.