Scenario 2: Checking and correcting the postal code, city and street, as well as rejecting the unfeasible - 6.1

Talend Components Reference Guide

Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
Data Governance
Data Quality and Preparation
Design and Development
Talend Studio

This scenario is closely related to the one above. But the difference is that, the addresses that cannot be assigned are written into a separate file for manual checking. Additionally, to write ambiguous addresses in a separate file, the procedure is the same as described here.

  1. Create a job as described in the previous scenario.

  2. Drag the following additional components from the Palette into the design workspace: tMap and tFileOutputDelimited.

  3. Double-click tUniservRTPost to open its Basic settings view.

  4. Select the Use rejects check box and enter "5" in the field if result class greater or equals to. This is the result class from the check of postal codes in addresses, which contain too few or unfeasible data.

  5. Connect tUniservRTPost with tMap_5 via Row > Rejects.

  6. Connect tMap with tFileOutputDelimited via Row > Main.

  7. Define the fields for the output file in the mapping window.