CheckForeignKey

Not available in Community Designer

Short Description
Ports
Metadata
CheckForeignKey Attributes
Details
Examples
See also

Short Description

CheckForeignKey checks the validity of foreign key values and replaces invalid values by valid ones.

ComponentSame input metadataSorted inputsInputsOutputsEach to all outputsJavaCTLAuto-propagated metadata
CheckForeignKey-
no
21-2-
no
no
no

Ports

Port typeNumberRequiredDescriptionMetadata
Input0
yes
For data with a foreign keyAny1
1
yes
For data with a primary keyAny2
Output0
yes
For data with a corrected keyInput 0
1
no
For data with an invalid keyInput 0

Metadata

Metadata cannot be propagated through this component.

CheckForeignKey has no metadata template.

Metadata on both input ports can be different. Metadata on the output(s) are usually the same as those on the first input port. They must at least have the same metadata structure (the number of fields, data types and sizes). Field names may differ.

CheckForeignKey Attributes

AttributeReqDescriptionPossible values
Basic
Foreign keyyes

A key according to which both incoming data flows are compared and data records are distributed among different output ports. For more information, see Foreign Key.

 
Default foreign keyyes

A sequence of values corresponding to the Foreign key data types separated from each other by a semicolon. Serves to replace invalid foreign key values. For more information, see Foreign Key.

 
Equal NULL 

By default, records with null values of fields are considered to be different. If set to true, nulls are considered to be equal.

false (default) | true
Advanced
Hash table size 

A table for storing key values. Should be higher than the number of records with unique key values.

512 (default) | properties
Deprecated
Primary key 

A sequence of field names from the second input port separated from each other by semicolon. For more information, see Deprecated: Primary Key.

 

Details

CheckForeignKey receives data records through two input ports.

The data records on the first input port are compared with those one the second input port. If a value of the specified foreign key (input port 0) is not found within the values of the primary key (input port1), the default value is given to the foreign key instead of its invalid value. Then all foreign records are sent to the first output port with the new (corrected) foreign key values and the original foreign records with invalid foreign key values can be sent to the optional second output port if it is connected.

Foreign Key

The Foreign key is a sequence of individual assignments separated from each other by a semicolon. Each of these individual assignments looks like this: $foreignField=$primaryKey.

To define Foreign key, you must select the desired fields in the Foreign key tab of the Foreign key definition wizard. Select the fields from the Fields pane on the left and move them to the Foreign key pane on the right.

Foreign Key Definition Wizard (Foreign Key Tab)

Figure 63.1. Foreign Key Definition Wizard (Foreign Key Tab)


When you switch to the Primary key tab, you will see that the selected foreign fields appeared in the Foreign key column of the Foreign key definition pane.

Foreign Key Definition Wizard (Primary Key Tab)

Figure 63.2. Foreign Key Definition Wizard (Primary Key Tab)


You only need to select some primary fields from the left pane and move them to the Primary key column of the Foreign key definition pane on the right.

Foreign Key Definition Wizard (Foreign and Primary Keys Assigned)

Figure 63.3. Foreign Key Definition Wizard (Foreign and Primary Keys Assigned)


You must also define the default foreign key values (Default foreign key). This key is also a sequence of values of corresponding data types separated from each other by a semicolon. The number and data types must correspond to metadata of the foreign key.

If you want to define the default foreign key values, you need to click the Default foreign key attribute row and type the default values for all fields.

Deprecated: Primary Key

In older versions of CloverETL, you had to specify both the primary and the foreign keys using the Primary key and the Foreign key attributes, respectively. They had a form of a sequence of field names separated from each other by a semicolon. However, the use of Primary key is deprecated now.

Examples

Checking City Names of Branch Offices

Check list of customers for cities without our branch office.

List of customers

John Doe        | London
Lucy Brown      | Glasgow
Elisabeth Smith | Stratford-upon-Avon
...

List of cities with our branch office

Edinburgh
Glasgow
London
...
Solution

Pass the list of customers (CustomerName and BranchOfficeCity) to the first input port and the list of cities with branch offices to the second input port.

Use the Foreign key and Default foreign key attributes.

AttributeValue
Foreign key$BranchOfficeCity=$city
Default foreign keyNot Found;

If a city from the list of customers was not found in the list with branch office cities, we changed the city name to Not Found.

See also

Common Properties of Components
Specific Attribute Types
Others Comparison