4. tJava
● Executes arbitrary Java code
● Can use external libraries
● Useful for small non-repeating tasks
● No re-usability
● No visibility, unlike other components ex.
MySQL input is for reading data from MySQL
with defined schema.
7. tGroovy
Same as tJava, executed arbitrary Groovy
code.
tGroovyFile reads the script from a file.
8. User Defined Routines
● Separate Java classes with static methods in
Talend project
● Suitable for small repeating tasks
● Little visibility based on class and method name
● Generally used from tMap or other code editor,
code components or inside other components.
Ex. Extract file name from string to feed into
tFileDelimetedInput.
9. Custom Components
● New components like built-ins in pallate.
● Suitable for tasks like support for extract/load
to/from new data source. Ex. Elasticsearch
● Or, custom processing, Ex pivot rows or convert
rows to nested JSON Mustache template
● Provides visibility, as a component has unique
icon to identify in ETL flow and its purpose is
understood.
10. Custom Components contd.
● Its reusable, as it will appear in pallate like
other built-in components and,
● It can be shared with other developer elegantly.
– Through Talend Forge
– Can export with Talend project and other user
import it with project
– Install it on TAC