Row connection

This type of row connection is the most commonly used connection. It passes on data flows from one component to the other, iterating on each row and reading input data according to the component properties setting (schema).

Data transferred through main rows are characterized by a schema definition which describes the data structure in the input file.

To connect two components using a Main connection, right-click the input component and select Row > Main on the connection list.

Alternatively, you can click the component to highlight it, then right-click it or click the arrow icon that appears on side of it and drag the cursor towards the destination component. This will automatically create a Row > Main type of connection.

For information on using multiple Row connections, see Multiple Input/Output.

This row connection connects a sub-flow component to a main flow component (which should be allowed to receive more than one incoming flow). This connection is used only in the case of multiple input flows.

A Lookup row can be changed into a main row at any time (and reversely, a main row can be changed to a lookup row). To do so, right-click the row to be changed, and on the pop-up menu, click Set this connection as Main.

Related topic: Multiple Input/Output.

This row connection connects specifically a tFilterRow component to an output component. This row connection gathers the data matching the filtering criteria. This particular component offers also a Reject connection to fetch the non-matching data flow.

This row connection connects a processing component to an output component. This row connection gathers the data that does NOT match the filter or are not valid for the expected output. This connection allows you to track the data that could not be processed for any reason (wrong type, undefined null value, etc.). On some components, this connection is enabled when the Die on error option is deactivated.

This row connection connects a tMap component to an output component. This connection is enabled when you clear the Die on error check box in the tMap editor and it gathers data that could not be processed (wrong type, undefined null value, unparseable dates, etc.).

Related topic: Handling errors.

This row connection connects a tMap component to one or several output components. As the Job output can be multiple, you get prompted to give a name for each output row created.

Related topic: Multiple Input/Output.

These row connection connect a tUniqRow to output components.

The Uniques connection gathers the rows that are found first in the incoming flow. This flow of unique data is directed to the relevant output component or else to another processing subJob.

The Duplicates connection gathers the possible duplicates of the first encountered rows. This reject flow is directed to the relevant output component, for analysis for example.

Some components help handle data through multiple inputs and/or multiple outputs. These are often processing-type components such as the tMap.

If this requires a join or some transformation in one flow, you want to use the tMap component, which is dedicated to this use.

For further information regarding data mapping, see Mapping data flows.

This type of row connection connects one CombinedSQL component to another.

When right-clicking the CombinedSQL component to be connected to the next one, select Row > Combine.