Jobs
A process flow that consists of one or more steps that execute tasks such as transformations, scripts, email notifications, file transfers, etc
In most ETL tasks you need to be able to perform maintenance tasks, orchestrate the execution of the transformations, and handle errors and retries. These tasks are handled by Jobs. A job consists of one or more job entry that are executed in a specific order. The order of the execution is determined by the job hops between the job entries as well as the executions themselves. Job entries differ in several ways:
You can create shadow copies of a job entry. This allows to place the same job entry in a job on multiple locations.
A job entry passes a results object between job entries. This means that once a job entry has been completed all rows are transferred at once, rather than in a streaming fashion.
Job entries are executed in a certain sequence (except if set to parallel execution)
Besides the execution order, a hop also specifies the condition on which the next job entry will be executed. You can specify the Evaluation mode by right clicking on the job hop. A job hop is just a flow of control. Hops link to job entries and, based on the results of the previous job entry, determine what happens next.
Workshops
Start off with an overview of the components that define a Job.
Create a Job that executes the 'hello world' transformation.
START
Job Entry
Last updated
