tCollector

Feeds the parallel execution processes with the threads generated by tPartitioner.

Note that
Talend Studio
also enables the automatic implementation of parallelization across a
Job without use of the parallelization components and we recommend using that approach. For
further information, see the section describing how to enable parallelization of data flows
of the
Talend Studio User Guide. However,
if you need to understand how to use these specific parallelization components, bear in mind
that the parallelization components work closely with each other to accomplish parallel
execution on given processes: the tPartitioner component
dispatches the input records into a specific number of threads; the tCollector component sends these threads to its following components for
parallel execution; the tDepartitioner component regroups
the outputs of the processed parallel threads; the tRecollector component captures the output of a given tDepartitioner component and sends the captured data to the next
component.

This component receives parallel threads from tPartitioner and sends those threads to
the following components for parallel execution.

tCollector Standard properties

These properties are used to configure tCollector running in the Standard Job framework.

The Standard
tCollector component belongs to the Orchestration family.

This component is available in the Palette of the
Integration
perspective of the Studio only if you have subscribed
to one of the
Talend Platform
solutions or Big Data
solutions.

Basic settings

Schema and Edit Schema	A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available: View schema: choose this option to view the schema only. Change to built-in property: choose this option to change the schema to Built-in for local changes. Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the [Repository Content] window.

Schema and Edit
Schema

A schema is a row description, it defines the number of fields to be processed and
passed on to the next component. The schema is either Built-in or stored remotely in the
Repository.

Click Edit schema to make changes to the schema.
If the current schema is of the Repository type, three
options are available:

View schema: choose this option to view the
schema only.
Change to built-in property: choose this
option to change the schema to Built-in for
local changes.
Update repository connection: choose this
option to change the schema stored in the repository and decide whether to propagate
the changes to all the Jobs upon completion. If you just want to propagate the
changes to the current Job, you can select No
upon completion and choose this schema metadata again in the [Repository Content] window.

Advanced settings

tStatCatcher Statistics	Select this check box to collect the log data at the component level.

Global Variables

Global Variables	ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box. NB_LINE: the number of rows processed. This is an After variable and it returns an integer. THREAD_ID: the ID of the thread this component is processing. This is available as a Flow variable. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it. For further information about variables, see Talend Studio User Guide.

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

NB_LINE: the number of rows processed. This is an After
variable and it returns an integer.

THREAD_ID: the ID of the thread this component is
processing. This is available as a Flow variable.

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage

Usage rule	This component should be put after tPartitioner with the Start link connecting each other. This component starts the parallel processes, in a Job, that you design using other components.
Connections	Outgoing links (from this component to another): Row: Main. Incoming links (from one component to this one): Trigger: Start. For further information regarding connections, see Talend Studio User Guide.

Usage rule

This component should be put after tPartitioner with the Start link connecting each other.

This component starts the parallel processes, in a Job, that you
design using other components.

Connections

Outgoing links (from this component to another):

Row: Main.

Incoming links (from one component to this one):

Trigger: Start.

For further information regarding connections, see

Talend Studio User
Guide.

Related scenario

For a related scenario, see Scenario: sorting the customer data of large size in parallel.

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 6.x

0 Comments

Inline Feedbacks

View all comments

tCollector – Docs for ESB 6.x