ParallelMerge gathers data records from multiple CloverDX Cluster workers. The algorithm of the component is derived from the regular Merge component.
|Input||0||For input data records||Any|
|Output||0||For gathered data records||Input 0|
ParallelMerge propagates metadata in both directions. The component does not change metadata priorities.
The component has no metadata template.
The component does not require any specific metadata fields on its ports.
ParallelMerge has same attributes as Merge. See Merge Attributes.
ParallelMerge gathers data records from multiple CloverDX Cluster workers.
The algorithm of this component is derived from the regular Merge component. For more details about attributes and other component specific behavior, see the documentation of the Merge component
This component belongs to a group of cluster components that allows the change from a multiple-workers allocation to a single-worker allocation. So the allocation of the component preceding the ParallelMerge component can provide multiple workers. The allocation of the component following the ParallelMerge component has to provide a single worker.
For more information about this component, see the CloverDX Cluster documentation (part of CloverDX Server documentation).
|3.4||The component is available since version 3.4.|
|4.3.0-M2||ClusterMerge was renamed to ParallelMerge.|