# tPartitioner Partitions the input data before tCollector can transfer them to the parallel execution processes. The tPartitioner splits the input records into a given number of threads which tCollector sends for parallel execution. Note that Talend Studio also enables the automatic implementation of parallelization across a Job without use of the parallelization components and Talend recommends using that approach. For further information, see [Enable parallelization of data flows](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/enabling-parallelization-of-data-flows). 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 is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio). ## tPartitioner Standard properties These properties are used to configure tPartitioner running in the Standard Job framework. The Standard tPartitioner component belongs to the Orchestration family. This component is available in Talend products with Big Data, Talend Data Management Platform, Talend Data Services Platform, and Talend Data Fabric. ## Basic settings | Properties | Description | | --- | --- | | 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:



Click Sync
columns to retrieve the schema from the previous component connected in the
Job. | | Number of Child Threads | Enter the number of threads you want to split the input records up
into.

We recommend that this number be N-1 where N is the total number
of CPUs or cores on the machine processing the data. | | Buffer Size | Enter the number of rows to be processed before the memory is freed.

This is the number of rows to cache for each of the threads
generated. | | Use a key hash for partitions | Select this check box to use the hash mode to dispatch the input
records into threads.

Once selecting it, the Key
Columns table appears, in which you set the column(s)
you want to apply the hash mode on. In the hash mode, the records
meeting the same criteria are dispatched into the same threads.

If you leave this check box clear, the dispatch mode is
Round-robin, meaning records are dispatched one-by-one to each
thread, in a circular fashion, until the last record is dispatched.
Be aware that this mode cannot guarantee that records meeting the
same criteria go into the same threads. | ## Advanced settings | Properties | Description | | --- | --- | | tStatCatcher Statistics | Select this check box to collect the log data at the component
level. | ## Global Variables | Variables | Description | | --- | --- | | 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 checkbox is
cleared, if the component has this checkbox.


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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component should be put after the input component(s) and
before tCollector.

This component uses and can only use the Trigger > Start link to connect to tCollector. | | Connections | Outgoing links (from this component to another):


Trigger: Start.

Incoming links (from one component to this one):


Row: Main.

For further information regarding connections, see [Using connections in a Job](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/using-connections-in-job). | **Related concepts** * [Sorting the customer data of large size in parallel](https://help.qlik.com/talend/en-US/components/8.0/orchestration/tdepartitioner-tpartitioner-trowgenerator-sorting-customer-data-of-large-size-in-parallel-standard-component-platform-the-job)