Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently, when falcon instance is rerun, we check if the workflow for given instance is present and just use oozie's workflow rerun.
However users might need coord reruns instead of workflow reruns,
1. Users may want to change job conf (hadoop conf) etc, with workflow reruns, exactly the same hadoop job is retried, but with coord rerun a new workflow instance is created with confs.
2. Users might use EL expressions like latest(0), which should be resolved again with new set of datasets.
3. Users might also need to re-evaluate dependencies in cases we have chain of jobs. With just workflow rerun the job simply kicks-off without checking for data.
Provide option like refresh and invoke coord rerun with refresh.
Attachments
Issue Links
- is related to
-
FALCON-1571 Falcon retry is happening infinitely in case of sub workflow getting killed.
- Open