Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Abrie_M
Contributor III
Contributor III

Qlik Compose: Drop and Recreate tables and Recreate views

Good day

In the previous version of Compose for Data Lakes, there was an option to Drop and Recreate specific tables.

In the current Qlik Compose, the only option is to drop and recreate all the tables and views. There is only one option to recreate views, for all tables. Any reason why the option for specific tables have been removed?

Thanx!

Labels (1)
1 Solution

Accepted Solutions
Nanda_Ravindra
Support
Support

Hi there,

    In Compose for Data Lakes which we refer to as Gen1 solution, we had the option to drop a specific table to support a reload of a replicate table in Compose. Meaning when a table is reloaded in replicate, you would drop that specific table in compose and then manually adjust the task and reload the table in compose.

In Qlik Compose which we refer to as Gen2 solution, if you reload a table in Replicate, you just run the CDC task in Compose and it will automatically handle the reload operation.

Replicate sends a message in ATT_CDC_REP_PARTITIONS that tells Compose a table has been reloaded, and the CDC process just picks up and processes the reload.  This way you don’t need to do anything special like you do in Compose for Data Lakes.

Since Qlik Compose handles the reload automatically now, we removed the option of dropping a specific table in Compose.

Hope this helps!

Thanks,

Nanda

 

 

View solution in original post

3 Replies
Noradavis
Contributor
Contributor

Compose enable you to drop and recreate the Storage Zone tables as required. When changing certain project settings (e.g. table prefixes) drop and create is ...

Generally speaking, you  space bar clicker   should not need to recreate the views very often. Usually, recreating the views is only required after upgrading to a newer Compose ...

Abrie_M
Contributor III
Contributor III
Author

Thanx, I saw that in the manual. We've had issues in the past on the previous version of Compose for Data Lakes where we needed to reload a table on Replicate, and then also on Compose.

In the new version, I understand whenever a table is reloaded in Replicate, it will automatically be reloaded with the next Compose run. The table is not dropped and the data is just added, so no history is lost.

Will have to get used to the new functionality, so that it does not impact our production system.

 

I still prefer the option to drop and recreate specific tables. Maybe I just feel more in control  🙂

Nanda_Ravindra
Support
Support

Hi there,

    In Compose for Data Lakes which we refer to as Gen1 solution, we had the option to drop a specific table to support a reload of a replicate table in Compose. Meaning when a table is reloaded in replicate, you would drop that specific table in compose and then manually adjust the task and reload the table in compose.

In Qlik Compose which we refer to as Gen2 solution, if you reload a table in Replicate, you just run the CDC task in Compose and it will automatically handle the reload operation.

Replicate sends a message in ATT_CDC_REP_PARTITIONS that tells Compose a table has been reloaded, and the CDC process just picks up and processes the reload.  This way you don’t need to do anything special like you do in Compose for Data Lakes.

Since Qlik Compose handles the reload automatically now, we removed the option of dropping a specific table in Compose.

Hope this helps!

Thanks,

Nanda