Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Goals

Ability to specify condition for execution-path in the hydrator pipelines.

Checklist

  • User stories documented (Shankar/Sagar)
  • User stories reviewed (Nitin)
  • Design documented (Shankar/Sagar)
  • Design reviewed (Terence/Andreas)
  • Feature merged ()
  • Examples and guides ()
  • Integration tests () 
  • Documentation for feature ()
  • Blog post

Use-case

User has a multi job pipeline, set of transforms run as a part of MR job doing data cleansing and a spark ML job on training data to output model. wants to add a conditional node after data cleansing, if there were less than 100 records that failed the preprocessing, he likes to continue running spark ML job, else he wants to send an email to the data engineer.

 

User-Stories

 

  • Pipeline developer wants to add a conditional node after one job before running the next job. 
  • Pipeline developer wants to add a conditional node at the end of the pipeline and optionally send an email if there were any errors in the final stage.
  • Pipeline developer wants to configure the conditional node with his custom code logic.   




  • No labels