Hi, Dlmuthu We have plan to add conditional workflow support into our task framework, where you can specify next job to execute based on previous job's status (succeed or failed or aborted, etc). But before we having that feature ready, one workaround you can do is to create two separate workflows containing only JobD and JobE in each, and start one of these workflows within your JobA depends on the output of JobA.
Thanks Lei On Fri, Nov 17, 2017 at 6:18 AM, DImuthu Upeksha <[email protected] > wrote: > Hi Devs > > I'm implementing a workflow similar to following image (copied from [1]). > When the workflow is started, Job A is executed. Depending on the result of > Job A, it should decide the next job to be executed (JobD or JobE). For > example, JobA checks for a database entry and if an entry can be found, > execute JobD otherwise execute JobE. As far as I have understood, we can do > the static wiring of jobs at the workflow creation phase. Is it possible to > perform above task in Helix? > [1] http://helix.apache.org/0.6.9-docs/tutorial_task_framework.html > > ​Thanks > Dimuthu >
