Version

    ParallelMerge

    Short Description
    Ports
    Metadata
    Details
    Compatibility
    See also

    Short Description

    ParallelMerge gathers data records from multiple CloverDX Cluster workers. The algorithm of the component is derived from the regular Merge component.

    ComponentSame input metadataSorted inputsInputsOutputsJavaCTLAuto-propagated metadata
    ParallelMerge
    yes
    yes
    1[1]1
    no
    no
    yes

    [1]  The single input port represents multiple virtual input ports.

    Ports

    Port typeNumberRequiredDescriptionMetadata
    Input0
    yes
    For input data recordsAny
    Output0
    yes
    For gathered data recordsInput 0

    Metadata

    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 Attributes

    ParallelMerge has same attributes as Merge. See Merge Attributes.

    Details

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

    [Note]Note

    For more information about this component, see Chapter 41, Data Partitioning in Cluster.

    Compatibility

    VersionCompatibility Notice
    3.4The component is available since version 3.4.
    4.3.0-M2ClusterMerge was renamed to ParallelMerge.