Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
tale103108
Contributor III
Contributor III

What is the difference between context_param from the command-line and contexts within Talend that are populated by a file?

Linux 6.3

Talend 6.2

---------------

 

What is the difference between context_param from the command-line and contexts defined within Talend that are populated by a file?

Does context_param overwrite or take precedence over a context loaded from within a Talend job (via a file context load)? Or vice-versa?

Does context_param 'create' a context (variable) or does one have to be defined within the Talend metadata prior to using context_param from the command-line?

 

Labels (1)
2 Replies
TRF
Champion II
Champion II

Hi,

The order the context variables are populated is (not absoluty sure between 2 and 3):

  1. "context".properties file (when launching autonomus script)
  2. command line (when launching autonomus script) - this overwrite 1
  3. file or database when using implicite tContextLoad (tab job, extra) (set when job starts)
  4. explicite tContextLoad (using component) or tJava (set during job run)

In any case, variables must be define in the jobs else they can't be used (compilation error).

So, they are never created "on demand", just populated.

 

Regards,

 

TRF
Champion II
Champion II

@tale103108, thank's for the Kudo.

You may also mark your case as solved if you found the answer were helpful.