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

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Lorenzo5
Creator
Creator

Triggering a Job specifying specific context variables

Hi,

let's suppose to have a quite complex parametric Job, for example one loading and aggregating the same kind of data, configurable for what is related to "which source" (of the same type, i.e. just different servers) and "which aggregation" (i.e. minute, hour, day... that is just a parameter in an SQL query).

You would like to trigger it hourly, daily... letting it which server use and which aggregation perform, differently for each trigger type, but you would not to deploy the same job in different tasks, to be able to set source/aggregation differently for each task, and triggering each task with it own trigger.

Should be useful, and compliant with the philosophy of Talend, to be able to specify a 'set of context values' for each trigger created?
In this way, you would be able to deploy a fully configurable Job just in one task instance, create on them multiple triggers and deeply specify which context values have to be applied for each trigger.

Does it worth a new Feature Request? 

Thank you,
Lorenzo

Labels (2)
2 Replies
Anonymous
Not applicable

Hi  Lorenzo,
Your job requirement is not clear for us. Do you want to trigger your job based on "Context" value? Could you please elaborate your case with an example?
Bets regards
Sabrina
Lorenzo5
Creator
Creator
Author

Hi Sabrina, 
I would trigger my job using a specific context for each trigger created. It could be very useful to setup the job depending on which trigger will run it.
Simply suppose to have a complex job that implements a very common task (for example calculating data average, xx-th percentile and some other figures), and you have to trigger it hourly, daily, weekly, monthly.
Suppose that your job is quite complex, and you would not split it in different jobs, because managing some calculations in one central place (a job) is your choice. Then, you have designed a job with some configuration parameters (contexts) that drive the job execution.
Suppose, then, you would calculate 99th percentile for the hourly and daily execution (two triggers involved), clean some data (or load some data) each day (the daily trigger involved), write a report file each week... and so on. The job is designed to do all these roles, because they are all related to the topic of the job.
For this reason, you would like that any trigger is able to pass to the job a different set of context values, otherwise you should put inside the job some "if" ("if it is the first hour of the day then clean something" ...) and it is bad, of course.

I know probably I can design my jobs in different manner, avoiding they perform complex and multiple computations/tasks, maybe designing simple ones, with dependencies (using "Execution Plan" or simply "tRunJob" to make dependencies and subsequential executions), but, I think, triggers could bring to the Job also some informations (i.e.: a set of context value). Could it add to much "degrees of freedom" to Talend? 

Thank you, Lorenzo