merger
Icon |
|
|---|---|
Use When |
Different instances of model based records need to be merged into a single instance that combines the attributes from all instances. |
Samples |
Normalized Table to Denormalized File |
Description |
The Merger component takes different instances of entities (records) and merges them together based on a set of join criteria. |
Inbound Message Type |
Model Based Message |
Output Message Type |
Model Based Message |
Control Message Handling |
Input: As entity messages are received this component will begin to join the data until the Unit of Work Boundary is received then the messages will be forwarded. Output: A single control message will be forwarded to downstream components once all messages have been processed through this step. |
| Name | Description |
|---|---|
Whether to forward failed messages and continue processing. This is the name of a linked component to forward the failed messages to. |
|
Double clicking on the Merger component in the flow will result in the Merger editor being displayed as shown below. The Merger editor displays a row for every entity/attribute in the input model and allows the selection of the columns on which to use as the key for the merge.
Model with Entity DENORMALIZED_PERSON having the following attributes:
* ADDRESS1 * ADDRESS2 * CELL_PHONE * CITY * FIRST_NAME * GENDER * HOME_PHONE * LAST_NAME * POSTAL_CODE * STATE * WORK_PHONE
A merger component with two sources, Person and Address Mapper which sends the following columns:
* ADDRESS1 * ADDRESS2 * CITY * FIRST_NAME * GENDER * LAST_NAME * POSTAL_CODE * STATE
The second source to the merger is the Home Phone Mapper which sends the following columns:
* FIRST_NAME * LAST_NAME * HOME_PHONE
The merge criteria selected on the Component Editor is
* FIRST_NAME * LAST_NAME
The merger will merge rows with the same FIRST_NAME and LAST_NAME, combining their attributes into a single entity instance (record), and then forward that record to downstream components.