Skip to main content
Announcements
Qlik Introduces a New Era of Visualization! READ ALL ABOUT IT

Loop Statement in Qlik Compose, tasks take longer than expected to load data

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
sureshkumar
Support
Support

Loop Statement in Qlik Compose, tasks take longer than expected to load data

Last Update:

Apr 8, 2024 3:53:29 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 8, 2024 3:53:29 AM

Qlik Compose logs statements such as: 

2024-03-11 18:38:24.056 [engine ] [INFO ] [] PI# 36 RUN : Adding staging rows to TSTG_E2LIS_02_ITM_P

18:38:30.431 [engine ] [INFO ] [] PI# 39 RUN : Loop Back Point.
pool-2-thread-3 2024-03-11 18:38:30.431 [engine ] [INFO ] [] Loop on 35,36,37,38

Loop Statements run in an iteration manner, which can lead to performance issues and tasks taking longer to load data. 

Resolution

Compose runs the process step (Adding staging rows to TSTG_E2LIS_02_ITM_P) in an iteration manner when any of the columns are not mapped. Either we have to map this column or define an expression for this column and regenerate the statements. Hence the process step will not be in the loop.

  1. In the below example (Job E01 Initialization Map_2LIS_02_ITM) some of the columns are not mapped

    manage data warehouse tasks Initialization.png

    unmapped columns.png


  2. In the Task Statements, we see the Loop Statements

    task statements and loop statements.png

  3. Once the columns are mapped and the task statements regenerated, the loop statements are removed

    mapping columns.png

    no more loop statements.png

    After mapping the missed columns, the task can be able to load the data faster.

Cause

Compose runs the process step (Adding staging rows to TSTG_E2LIS_02_ITM_P) in an iteration manner when any of the columns are not mapped.

Internal Investigation ID(s)

QB-21468
QB-25783

 

Environment

Labels (1)
Version history
Last update:
‎2024-04-08 03:53 AM
Updated by: