Skip to main content Skip to complementary content

Step 3: Reference file definition, remapping, inner join mode selection

Procedure

  1. Define the metadata corresponding to the LosAngelesandOrangeCounties.txt file in the same way described in Step 6 of Step 1: Job creation, input definition, file reading using the wizard.

    At Step1 of the wizard, name this metadata entry as LA_Orange_cities.

  2. Drop the newly created metadata to the top of the design area to create automatically a reading component pointing to this metadata.
  3. Link this component to the tMap component.
    Screenshot of the Job in the Designer.
  4. Double-click again on the tMap component to open its interface. Note that the reference input table (row2) corresponding to the LA and Orange county file shows to the left of the window, right under the main input (row1).
  5. Define the join between the main flow and the reference flow.

    Drop the City column from your first input table onto the City column of your reference table to establish a join between the two files. A violet link displays, to materialize this join.

    Screenshot of the join you created in the tMap interface.
  6. Drop the County column from the right section (row2) onto the Expression field of the County column on the right section (out1).
    Screenshot of the mappings.
  7. Click the OK button to validate your changes and run the new Job.

    The following output should display on the console.

    Screenshot of the console after successfully running the Job.

    The last columns of some of the records are filled with Los Angeles and Orange while others are empty. The reason for this is that by default, the tMap implements a left outer join mode. If you want to filter your data to only display lines for which a match is found by the tMap, then open again the tMap, click the tMap settings button and select the Inner Join in the Join Model list on the reference table (row2).

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here