Icon

04.1_​ETL_​Customers

04.1_ETL_Customers_exercise
Extract Transform Load Session 4 OrchestrationExercise 04.1 ETL Customers 2 Handle errors1. Connect the Try (VariablePorts) node with the bothData Access components 3 Handle errorsVariable Creator node connected to Database Update component creates a flow variableETL_failed equal to 0. Second Variable Creator creates a flow variable ETL_failed equal to 11. Provide the variable ETL_failed = 0 to the upper port of the Catch Errors (Var Ports) node2. Provide the variable ETL_failed = 1 to the bottom port of the Catch Errors (Var Ports) node3. If the value of the flow variable ETL_failed is 1 (Case Switch Start node, flow variable ports),send an email to a responsible person (Send Email node). If you want to try the node out, provideyour credentials or leave it as a placeholder. 1 Import thecredentials1. Import flow variablesfrom the caller (WorkflowService Input, flow variableports) 4 Export workflow status1. Export the variable ETL_failed to thecalling workflow (Workflow ServiceOutput node, flow variable ports) ExercisesAll the tasks can be found in the yellow annotations and the yellow components.Make sure you have executed the 00_Setup_PostgreSQL_Database or 04.0_Reset_DB&Big_Data_Environment workflow before running this workflow. NOTE. This node can only beexecuted successfully whenthe current workflow is calledfrom the 04.3 Orchestrationworkflow. We recommendsolving these two exercisestogether.Blend the data fromdifferent sourcesStatus: failureStatus: successConcatenate Database Update Variable Creator Data Anonymization Data AccessUS Customers Data AccessEurope Customers Variable Creator Extract Transform Load Session 4 OrchestrationExercise 04.1 ETL Customers 2 Handle errors1. Connect the Try (VariablePorts) node with the bothData Access components 3 Handle errorsVariable Creator node connected to Database Update component creates a flow variableETL_failed equal to 0. Second Variable Creator creates a flow variable ETL_failed equal to 11. Provide the variable ETL_failed = 0 to the upper port of the Catch Errors (Var Ports) node2. Provide the variable ETL_failed = 1 to the bottom port of the Catch Errors (Var Ports) node3. If the value of the flow variable ETL_failed is 1 (Case Switch Start node, flow variable ports),send an email to a responsible person (Send Email node). If you want to try the node out, provideyour credentials or leave it as a placeholder. 1 Import thecredentials1. Import flow variablesfrom the caller (WorkflowService Input, flow variableports) 4 Export workflow status1. Export the variable ETL_failed to thecalling workflow (Workflow ServiceOutput node, flow variable ports) ExercisesAll the tasks can be found in the yellow annotations and the yellow components.Make sure you have executed the 00_Setup_PostgreSQL_Database or 04.0_Reset_DB&Big_Data_Environment workflow before running this workflow. NOTE. This node can only beexecuted successfully whenthe current workflow is calledfrom the 04.3 Orchestrationworkflow. We recommendsolving these two exercisestogether.Blend the data fromdifferent sourcesStatus: failureStatus: successConcatenate Database Update Variable Creator Data Anonymization Data AccessUS Customers Data AccessEurope Customers Variable Creator

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: Lada.Rudnitckaia
Created at: 2021-10-07
On NodePit since: 2022-11-12
Last update: 2024-04-27
Created with KNIME version: v4.5.2
Tags: Best practicesData engineerData engineeringEducation

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!