Skip to main content Skip to complementary content

Configuring the components

Procedure

  1. Double-click tGreenplumConnection to open its Basic settings view in the Component tab.
    1. In the Host and Port fields, enter the context variables for the Greenplum server.
    2. In the Database field, enter the context variable for the Greenplum database.
    3. In the Username and Password fields, enter the context variables for the authentication credentials.
    For more information on context variables, see Using contexts and variables.
  2. Double-click employee+statecode to open its Basic settings view in the Component tab.
    1. In the Default table name field, enter the name of the source table, namely employee_by_statecode.
    2. Click the [...] button next to the Edit schema field to open the schema editor.
    3. Click the [+] button to add three columns, namely id, name and statecode, with the data type as INT4, VARCHAR, and INT4 respectively.
    4. Click OK to close the schema editor.
    5. Link employee+statecode to tELTGreenplumMap using the output employee_by_statecode.
  3. Double-click statecode to open its Basic settings view in the Component tab.
    1. In the Default table name field, enter the name of the lookup table, namely statecode.
  4. Click the [...] button next to the Edit schema field to open the schema editor.
    1. Click the [+] button to add two columns, namely state and statecode, with the data type as VARCHAR and INT4 respectively.
    2. Click OK to close the schema editor.
    3. Link statecode to tELTGreenplumMap using the output statecode.
  5. Click tELTGreenplumMap to open its Basic settings view in the Component tab.
    1. Select the Use an existing connection check box.
  6. Click the [...] button next to the ELT Greenplum Map Editor field to open the map editor.
  7. Click the [+] button on the upper left corner and in the pop-up dialog box, select the employee_by_statecode table from the drop-down list and click OK .
    The input table employee_by_statecode is displayed on the left panel of the editor.

    Do the same to create the input table statecode.

  8. On the upper right corner, click the [+] button to add an output table, namely employee_by_state.
    1. Click Ok to close the map editor.
  9. Double-click tELTGreenplumOutput to open its Basic settings view in the Component tab.
    1. In the Default table name field, enter the name of the output table, namely employee_by_state.
  10. Click the [...] button next to the Edit schema field to open the schema editor.
    1. Click the [+] button to add three columns, namely id, name and state, with the data type as INT4, VARCHAR, and VARCHAR respectively.
    2. Click OK to close the schema editor.
    3. Link tELTGreenplumMap to tELTGreenplumOutput using the table output employee_by_state.
    4. Click OK on the pop-up window below to retrieve the schema of tELTGreenplumOutput.
    ow the map editor's output table employee_by_state shares the same schema as that of tELTGreenplumOutput.
  11. Double-click tELTGreenplumMap to open the map editor.
    D.
    Drop the columns id and name from table employee_by_statecode as well as the column statecode from table statecode to their counterparts in the output table employee_by_state.
    Click Ok to close the map editor.
    1. Drop the column statecode from table employee_by_statecode to its counterpart of the table statecode, looking for the records in the two tables that have the same statecode values.
  12. Double-click tGreenplumInput to open its Basic settings view in the Component tab.
    1. Select the Use an existing connection check box.
    2. In the Table name field, enter the name of the source table, namely employee_by_state.
    3. In the Query field, enter the query statement, namely "SELECT * FROM \"employee_by_state\"".
  13. Double-click tLogRow to open its Basic settings view in the Component tab.
    1. In the Mode area, select Table (print values in cells of a table for a better display.

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