You are not logged in.
In v4.0.2, there are two options for raising errors/warnings/info on tContextLoad, as follows:
1) A load variable does not exist in the local context (i.e. a new context variable is being created)
2) A pre-existing context variable is not being updated by any of the load variables
What I would dearly like is a third option:
3) A pre-existing context variable is being updated by a load variable.
This is by far the most important case for me. In this scenario, an existing hard-coded local value is being silently overwritten (!). This is a situation I want to know about. Indeed, I want the entire job to fail if this happens because this will almost certainly cause unexpected results.
Thanks for your support.
If you are any idea, please use the bugtraker to submit your feature.
To achieve ypur goal now (3), you can use the tContextDump to store context before and after tContextLoad, then you can ckeck the changes.
In fact, all pre existing context variables are updated by tContextLoad when context is in flow :
In Talend there are many way to set context variable :
In a job the first step is to read the context file ( DEFAULT.properties) with value set in context view of GUI
the second step is to read the value from the commanline with parameter --param_context.
Then with tContextLoad component.
In a job you can have the tRunjob, it can set context value to child job too