topic Re: Avoid initial loading after a table change in Qlik Replicate

Avoid initial loading after a table change

Vg21 — Fri, 19 Jul 2024 12:39:10 GMT

Hello all,

I've created a task with a few tables, my source is an Oracle database and its target is kafka.

I have ticked the "by default include all columns" checkbox in the "Table settings" for all tables in the task, but now I need to uncheck it.

My issue here is that I will have to reload all tables after such change.

Is there a way to avoid a full load in this case?

Re: Avoid initial loading after a table change

DesmondWOO — Sat, 20 Jul 2024 17:19:50 GMT

Hi @Vg21 ,

Thank you for reaching out to the Qlik Community.

Is it a Full Load + CDC task? If so, please disable Full Load in the task setting and try again.

Regards,
Desmond

Re: Avoid initial loading after a table change

Heinvandenheuvel — Tue, 23 Jul 2024 16:20:08 GMT

Once 'by default select all columns' is unselected, only the PK columns and any added column will remain.

It is really just a UI convenience knob: do you need most columns? use it and drop those columns not needed. Do you need only a few columns? disbale and add all columns you do need. The end result wll surely be the same: those colums you need.

I suppose you will disable and then add a few columns back. What would you like to have happen on the target? Leave those already-loaded-but-no-longer-selected columns there? Drop the undesired columns from the target? The easiest is of course to just let Replicate reload.

If you just want to move on, without reload, you can consider to edit, save, stop and RUN ADVANCED - BY TIMESTAMP TABLES ALREADY LOADED. Optionally- preferably you my want to manually drop the no longer desired columns on target preferably before the run. If you leave the no-longer-provided columns on target and they do not allow NULL, then CDC will fail of course as there is no value (NULL) for those colums.

Hein