1. Is it possible to schedule a coordinator where the interval between runs is automatic based on success?
Use case: this specific workflow self bootstraps with small iterative units of work and we would like for it to run the next one as soon as the previous one has finished with as small of a gap as possible. I know I could schedule it to have a reschedule interval of X (where X is the best case runtime) as a way around this but due to the runtime having a large range this could cause a large backfill of coordinator actions that would be scheduled and I don't know the implications of this. Is there a non-hacky way around this? 2. Is there a way to throw a specific error from a Java action which would cause the Oozie server to automatically retry the workflow? Use case: as it is we have several workflows that have Java actions in them and we would like to use the auto retry logic built into the Oozie server. Currently if the Java main dies due to a custom / standard exception it does not trigger the auto retry and the documentation isn't very clear on how to bridge the gap. Thank you for any advice on either! Brad M.
