ParallelPartition distributes incoming data records among different CloverDX Cluster workers. The algorithm of the component is derived from the regular Partition component.
|Component||Same input metadata||Sorted inputs||Inputs||Outputs||Java||CTL||Auto-propagated metadata|
 The single output port represents multiple virtual output ports.
 ParallelPartition can use either a transformation or two other attributes (Ranges and/or Partition key). A transformation must be defined unless at least one of the attributes is specified.
|Input||0||For input data records||Any|
|Output||0||For output data records||Input 0|
ParallelPartition propagates metadata in both directions. The component does not change priority of propagated metadata.
The component has no metadata templates.
The component does not require any specific metadata fields on its ports.
ParallelPartition has same attributes as Partition. See Partition Attributes.
ParallelPartition distributes incoming data records among different CloverDX Cluster workers.
If the Ranges attribute is used for partitioning, the number of defined ranges must match the allocation of the following component. Use the and toolbar buttons to adjust the number of defined ranges:
This component belongs to a group of cluster components that allows the change from a single-worker allocation to a multiple-worker allocation. So the allocation of the component preceding the ParallelPartition component has to provide just a single worker. The allocation of the component following the ParallelPartition component can provide multiple workers.
For more information about this component, see the CloverDX Cluster documentation (part of the CloverDX Server documentation).
|3.4||The component is available since version 3.4.|
|4.3.0-M2||ClusterPartition was renamed to ParallelPartition.|