|CTL Templates for Joiners|
|Java Interfaces for Joiners|
Joiners serve to put together the records with potentially different metadata according to the specified key and the specified transformation.
Joiners have both input and output ports. The first input port is called master (driver), the other(s) are called slave(s).
Joiners join records from master port with particular records from error port. Joiners do not join records between slave ports.
They can join the records incoming through at least two input ports (ExtHashJoin, ExtMergeJoin, and RelationalJoin). The others can also join the records incoming through a single input port with those from lookup table (LookupJoin) or database table (DBJoin). In them, their slave data records are considered to be incoming through a virtual second input port.
Generally, joiners match on equality: all the join key fields from master must match the corresponding fields from slave.
RelationalJoin joins data records based on the non-equality conditions,
Joiners propagate metadata between master input port and output port for unmatched records. Joiners do not propagate metadata in any other direction.
Joiners have no metadata templates.
You must assign metadata on input edges to be able to specify the transformation. The metadata on the output edge can be created and edited in transformation editor.
These components use a transformations that are described in the section concerning transformers. See Defining Transformations for detailed information about how transformation should be defined. All of the transformations in Joiners use common transformation template (CTL Templates for Joiners) and common Java interface (Java Interfaces for Joiners).
Here is an overview of all Joiners:
Table 58.1. Joiners Comparison
|Component||Same input metadata||Sorted inputs||Slave inputs||Outputs||Output for drivers without slave||Output for slaves without driver||Joining based on equality||Auto-propagated metadata|