Subjob combination logic (graphical sense)

[GSpringer]

Simple question about the way Talend combines subjobs.  What logic dictates Talend Studio auto-combining subjobs?  

I built these two jobs similarly, but while building them one (the first) absorbed the bottom three buttons into the top subjob, the other left them separate.  Just looking for the logic behind how to combine/separate subjobs.  In this case it doesn't really matter, I'm just curious, would be useful for bigger jobs to understand.

[nfz11 · Accepted solution]

This is an interesting question.  I would expect that both flows would show as two sub jobs because of the 'On Component OK' trigger.

A few questions:

• Does the first job break up into two sub jobs if you add a third input?
• What is the yellow warning in the 'qdw_codes' component?
• What is the difference between the two jobs besides three versus two inputs?
• Are the two jobs in separate files or in one file?
• Can you attach an export of the jobs?

Thanks.

[GSpringer]

Thanks nfz11,

Strangely enough when I went to open the jobs today they each showed up with the components in one sub-job, so I can't test out what would happen if i changed them so well.

Besides the third input step there wasn't any difference.  The yellow flag was a "schema's dbtype does not match component", which I wasn't sure how to fix, but doesn't affect job results (at least in this instance!).

The jobs were contained in separate files, to my knowledge, (i.e. Insert_Dim_Codes 0.1, Insert_Dim_Location 0.1).

Thanks for the feedback

[nfz11]

Great, I am glad it fixed itself. I have seen other cases where Talend gets out of sync and a closing and reopening of the job fixes it.

Can you please mark this topic as resolved by selecting a solution if there is no more to be done? Thanks.