Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Multithread Looping

Hi,

I’m working with the function tRunJob of Talend Studio 6.4. On the project I’m working the idea is to run the same sub job several times with different parameters, to do so I defined the following job:

                                                                               tLoop----> tRunJob

The problem is that each one of the subjobs takes sometime to finish . Consequently the tLoop only does one iteration and stops waiting for the sub job to finish, in order to iterate one more time. I enabled the option “use an independent process to run sub job” and the multithread execution, but it doesn’t work, it only runs the first sub job and keeps waiting.

What can I do?

 

Thanks and regards

Labels (3)
4 Replies
Anonymous
Not applicable
Author

Hello,

You don't want any pause between each two executions?

The Job should contain multiple subjobs that are totally separated. No triggers link them.

To let these subjobs run in parallel, you need to select the Multi thread execution box.

 

Best regards

Sabrina

Anonymous
Not applicable
Author

Hi Sabrina,
Thanks for your response!

Actually, my question was, is there a way to intiate the 2nd, 3rd iteration
before prior iteration completes?
Anonymous
Not applicable
Author

Hello,

In the Iterate ,it will execute no.of times the downstream component based on the no.of records coming from the above component, where we define iterate.

By default, the 2nd iteration will be executed when prior iteration complete. Is enable parallel execution option unchecked?

Best regards

Sabrina

 

David_Beaty
Specialist
Specialist

Hi,

 

On the "Iterate" connection between the tLoop and the next component, you should be able to tick the option "Enable parallel execution" an additional box then appears with the number of execution threads - I strongly suggest you parameterise that value.

 

Consider though, whether the server you're running the job on is actually capable of running multiple instances of whatever the loop is doing.

 

Thanks

 

David