topic Re: Manually include a component in a subjob / create a unique subjob with several components in Talend Studio

Manually include a component in a subjob / create a unique subjob with several components

Alpha549 — Fri, 15 Nov 2024 23:01:29 GMT

Hello everyone,

Here is a job :

As we can see, we have 3 subjobs here. Is it possible to have one unique subjob including these 3 tJava ?

Thank you 🙂

Re: Manually include a component in a subjob / create a unique subjob with several components

Anonymous — Tue, 12 Apr 2022 00:52:55 GMT

Hello

There are different subjobs in this job, tJava_2 and tJava_6 will trigger tJava_4 execution with onComponentError connector, so, logically, you cannot include tJava_2 and tJava_6 in a child job called by tRunJob.

Regards

Shong

Re: Manually include a component in a subjob / create a unique subjob with several components

Alpha549 — Tue, 12 Apr 2022 01:02:20 GMT

Hello @Shicong Hong

I've updated the image to make it clearer !

What do you think ?

Re: Manually include a component in a subjob / create a unique subjob with several components

Anonymous — Tue, 12 Apr 2022 01:55:49 GMT

Move these tJava components to a child job, and use a tRunJob to call this job.

main job.

tRunJob(call the child job)

|onsubjobok

other subjob.

child job:

tJava1--oncomponnetok--tJava2---oncomponentok--tJava3

This is what you want?

Re: Manually include a component in a subjob / create a unique subjob with several components

Alpha549 — Tue, 12 Apr 2022 02:08:52 GMT

Yes it's a way to do so.

For instance, if we have this job :

If an error occurs in tJava_1, tJava_4 is run.

If an error occurs in tJava_2 or 3, the job fails.

This is because tJava_1 is a subjob. tJava_2 et tJava_3 are each a subjob.

I would like to have tJava_1, 2 and 3 in the same subjob, so I can use a unique OnSubjobError link to run tJava_4, without using tRunJob.

I know that if I want to catch errors in tJava_2 and 3, I should use onComponentError link from each of them to tJava_4, also from tJava_1 instead of onSubjobError. This solution will always work.