Talend Cloud not taking into account the correct context configuration in subjobs

[Kaiser_Soze]

Hello,

I am having as issue with Talend Cloud about the context variables that are used, let me explain :

I have created one context in the Talend Studio repository with 2 configurations :

Default : Context where I have set up the Windows filepaths I am using in the Development environment. 

         Example : //data//Morpheus/Transmitted/

Prod : Context where I have set up the CentOS filepaths I am using in the Production environment

         Example : /export/data/Morpheus/Transmitted/

When I execute my job in Talend Studio 7.3, everything works fine.

When I execute the job in Talend Cloud, in the main job, everything works fine BUT in the child job, even though every parameter is set up with the Prod context configuration, it is still taking into account filepaths corresponding to the Default context configuration and not to the Prod context.

Most surprisingly, when I delete the Default context, everything works fine in Talend Cloud. Which means it was really taking into account the Default configuration even though I was publishing the job with the Prod Context setup and when I specified the Prod path in the job configuration in Talend Cloud.

[Anonymous]

Hi

The variable name should be the same both in main job and child job, and make sure the 'transmit whole context' box is checked on tRunJob.

Refer to this topic, there should be an environment called Prod in TMC, and select the workspace from Prod in the workspace list when publish the job to Talend Cloud.

If there is only one environment in TMC, you can edit the task and customize the parameter value.

Regards

Shong

[Kaiser_Soze · Accepted solution]

Hello,

Yes the variable names are indeed the same in both main and child jobs.

Your suggestion works well, selecting the "Transmit whole context" solve the issue if this option suits your needs.

Nevertheless I have contacted the support team and basically, for those who can't select this option there is indeed a solution.

For those who already installed the R2021-07 (or later patches) for Talend Studio 7.3.1, you just have to configure the dynamic context option and for those who don't have just download the last patch for for Talend Studio 7.3.1 which is by the time I write this post the : R2021-11.

Here is the link where you can see the news functionalities implemented by the patches :

https://help.talend.com/r/fr-FR/7.3/release-notes-big-data-products/r2021-07-studio-new-features

The functionality that interests us here is the new "Dynamic context" option for subjobs.

I have posted in the attached file a screenshot that was given to me by the talend support team. It basically explains how you can implement it to pass the context group name dynamically.

Thanks for your help @shong and I hope our suggestion will help out more fellow talend users.