speaking about tRunJob Component, with "Transmit whole context" deselected I expect Child Job using their own values, Original or Custom that are, but when Custom Values are selected (in the Child Job) they are even ignored and the Child Job run with their default values.
This means that when I customise the value of a context parameter in the Child Job, and I want this impact any its execution, I have to change it also in any tRunJob component appointed to run the Child Job.
Furthermore, the 'context' parameter (designed to specify within which context the Child Job should run) is 'hard-coded' in the Parent Job, so it cannot depend to on which environment the job has been deployed.
It is not so good, in my opinion (as far as I know contexts are designed to adapt jobs to different environments), and I think we should able to set the "context" as "parent context", in someway.
(Talend version: 6.2)
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables