Which components are most important to you certainly depends on the learning objectives of this tool and the processes that you will build in the future. For some, components related to a particular technology, e.g. Teradata, will be very important, but for others they will be completely unnecessary. However, there is a group of components that you will need to know, regardless of the technologies you work with and the learning objectives. In this part of the course, I will show you the most popular TOS DI components.
tMap is definitely one of the most used and overused components. It is used to transform, combine data from many sources, and transport them to one or many targets. In tMap you can use variables, you have simple and quick access to transform functions and you can easily filter the data sent to target objects.
tLogRow displays process results or loading data in the Run view. We can use it when testing process logic by checking live results in the console.
If you are building many integration processes, you will definitely want to run them in a specific order. And this is where tRunJob appears – it allows you to manage the job sequence.
As the name says, tFilterRow filters the input, allowing you to apply many conditions. It allows us to eliminate unnecessary data from further processing, for technical or business reasons.
tAggregateRow is responsible for aggregating data based on the indicated parameters of the component. Aggregation is possible based on many columns. From the available operations we have: count, min, max, avg, sum, first, last, list, count (distinct), union (geometry) and standard deviation.
tPreJob & tPostJob
When you build complex integration processes, you cannot do without tPreJob and tPostJob. The first one starts the work process and triggers the to-do task that will be started before the main data flow begins. tPostJob triggers the task or process to be started after the main task has been completed.
tSortRow sorts the input data based on one or more input columns according to the designated order and sort types.
The tFileList component interacts with a set of files or directories in a given folder based on a defined mask. It is possible to define the iteration order – depending on the modification date, file name or size, in descending or ascending order.
Although Talend DI currently has over 900 ready-to-use components, it often happens that the processing logic requires us to write some of our own code more suited to our needs. And because TOS DI was written in Java, the tJava component comes to our aid.
The tSendMail component is responsible for sending emails with the option of adding attachments. Certainly will help in sending notifications about the end of the process or errors arising during its working.
The explanation of components
These are just 10 of over 900 components created for the Talend Data Integration tool, but regardless of the components associated with source or target objects, they most often appear in work processes.
However, if you need support for other Talenda components and the Internet fails, you can use the short description and sample use-case of components provided by Talend. To do this, drag the selected component to the designer screen, and then press the F1 button. A new Help tab will appear.
By choosing tReplace corresponding to the name of the component you have chosen, its description will appear: