Bugzilla – Bug 4540
Batch and Exit status for splits
Last modified: 2013-01-23 21:25:09 UTC
In section 5.5.3 on page 41, the spec defines batch and exit statuses for a split. There are a couple issues with this:
1. Who provides the exit status for a Split?
2. A split is not a single unit of work to be restarted, etc. so what does giving it it's own status add (you restart the steps within a split but not the split as a whole)?
Since a Split is just a way to parallelize step execution, I would expect it to behave as if it didn't exist and delegate to the steps it wraps for things like statuses.
The only batch or exit status a split could have is derived from the flows (steps, really) that comprise the split.
I agree the spec offers no way to set an exit status for the split. The SplitAnalyzer did, but we did away with that after the public draft.
Batch status could be "calculated" based on the outcome of the flows, but ends up being either COMPLETED, FAILED, or STOPPED. But none of these are interesting, because the job will only continue if the status is COMPLETED.
So section 5.5.3 will be deleted.