tDepartitioner

Assembles the outputs of the parallel execution processes so that tRecollector can capture those outputs.

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 regroups the outputs of the parallel processes
executed by its preceding components.

tDepartitioner Standard properties

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

The Standard
tDepartitioner component belongs to the Orchestration family.

This component is available in Talend products with Big Data, Talend Data Management Platform, Talend Data Services Platform, Talend MDM Platform and Talend Data Fabric.

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. Click Sync columns to retrieve the schema from the previous component connected in the Job.
Buffer Size	Enter the number of rows to be processed before the memory is freed.

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.

Click Sync
columns to retrieve the schema from the previous component connected in the
Job.

Buffer Size

Enter the number of rows to be processed before the memory is freed.

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. 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.

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 is the end component of the parallel execution processes in a Job. This component requires tRecollector to be able to output the execution results.
Connections	Outgoing links (from this component to another): N/A Incoming links (from one component to this one): Row: Main. For further information regarding connections, see Talend Studio User Guide.

Usage rule

This component is the end component of the parallel execution
processes in a Job.

This component requires tRecollector to be able to output the execution
results.

Connections

Outgoing links (from this component to another):

N/A

Incoming links (from one component to this one):

Row: Main.

For further information regarding connections, see

Talend Studio User
Guide.

Related scenario

For a related scenario, see Sorting the customer data of large size in parallel.

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

Thank you for watching.

Docs 7.x

0 Comments

Inline Feedbacks

View all comments

tDepartitioner – Docs for ESB 7.x