During a Replicate Full Load, incoming changes occur while the Full load is in progress. What happens to those changes?
Qlik replicate starts the CDC thread before starting the Full load and all the changes show as cached events while the Full load is running. For example, 2 billion records are applied in the Full load state and Replicate again check at the end of the Full load for committed changes. If 100k changes are also committed before finished then it will also be applied in the full load otherwise the 100k changes will go to CDC.
Another example, for a full load takes 12 hours, then updates during the 12 hours full load window are also applied. Note- these two examples assume you have CDC enabled in the task.
If CDC is turned off during a full load task, then Replicate will not capture the cached events.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.