Suggest an Idea

[sanlamZA]

Our Cloudera DataLake holds data from various sources with no insight or control on the source data changes.

Currently when changing a Primary Key value in the source record it will cause a new record to be inserted in the storage table.

Due to this behavior our BI environment displays an huge amount of duplicate values when selecting from the storage base table or the current view.

We have a need for this behavior to change. A possible solution maybe to have a header deleted  value for the before image.

Thanks

Janine

[Abrie_M]

Good day 

Any update on this request?

Thanx

Abrie Marais

[Tzachi_Nissim]

Thank you. We are looking at addressing this in Replicate by turning the BEFOREIMAGE+UPDATE into a DELETE+INSERT when a PK change is involved. This is a relatively high priority item. I am putting this into "Collecting feedback" until we formally have this in the plan.

[Meghann_MacDonald]

This feature has been delivered in Qlik Replicate November 2022. Thank you for your contributions! Qlik Replicate can now deliver a PK update as a DELETE (prior key) and INSERT (new key) pair. Review the configuration - https://help.qlik.com/en-US/replicate/May2023/Content/Global_Common/Content/SharedEMReplicate/Custom...