Skip to main content Skip to complementary content
  • New archived content: Talend MDM, Talend Data Catalog 8.0, and Talend 7.3 products reached their end of life in 2024. Their documentation was moved to the Talend Archive page and will no longer receive content updates.
Close announcements banner

Calculating the incident occurrence

Procedure

  1. Double-click tAggregateRow to open its Component view.

    Example

  2. Click the [...] button next to Edit schema to open the schema editor.
  3. On the output side (right), click the [+] button twice to add two rows and in the Column column, rename them to incident_type and incident_number, respectively.

    Example

  4. In the Type column of the incident_number row of the output side, select Integer.
  5. Click OK to validate these changes and accept the propagation prompted by the pop-up dialog box.
  6. In the Group by table, add one row by clicking the [+] button and configure this row as follows to group the outputted data:
    • Output column: select the columns from the output schema to be used as the conditions to group the outputted data. In this example, it is the incident_type from the output schema.

    • Input column position: select the columns from the input schema to send data to the output columns you have selected in the Output column column. In this scenario, it is the incident_type column from the input schema.

  7. In the Operations table, add one row by clicking the [+] button once and configure this row as follows to calculate the occurrence of each incident type:
    • Output column: select the column from the output schema to store the calculation results. In this scenario, it is incident_number.

    • Function: select the function to be used to process the incoming data. In this scenario, select count. It counts the frequency of each incident.

    • Input column position: select the column from the input schema to provide the data to be processed. In this scenario, it is incident_type.

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!