Skip to main content Skip to complementary content
Close announcements banner

Creating and configuring the job

In Talend Studio, create a Big Data Streaming Job with one input payload (which will be of XML representation), one schema output, one payload output (which will be of XML representation), and the tHMapRecord.

Procedure

  1. Navigate to Job Designs > Big Data Streaming and create a job:
  2. Connect the components using Row > Main connection. Enter schemaOut and payloadOut respectively, when prompted for the output name.
  3. Select tFixedFlowInput to edit the schema.
    1. Add a new column pOut of String type.
    2. Click OK.
  4. Select the first tLogRow to edit the schema.
    1. Add two columns, a and b, of String type.
    2. Click OK.
    3. Click Sync columns.
  5. Select the second tLogRow to edit the schema.
    1. Add a column of String type.
    2. Click OK.
    3. Click Sync columns.
  6. Double-click the tHMapRecord component to configure the structure.
    1. For the row1 input connection, select the a payload structure from the wizard with an XML representation.
    2. For the payloadOut output connection, select a payload structure from the wizard with an XML representation.
      Talend Data Mapper automatically generates the corresponding structure of the schemaOut output connection because it has multiple columns. When you configure the payload structures, Talend Data Mapper automatically creates a map with a new multi-output or wrapper structure, which contains the selected payloadOut structure and a generated structure of AVRO representation for the schemaOut connection.
    The tHMapRecord map view opens.
  7. Map the input elements to the output elements:

    The input payload structure has an XML representation, while the multi-output or wrapper structure uses the first structure representation of the payload connection, which is XML in this case.

  8. Run the job.

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 – let us know how we can improve!