Bugzilla – Bug 4183
There is no way to access the parent job context at the end of a Split
Last modified: 2013-01-16 23:02:50 UTC
Analyzers, collectors, and Reducers are currently not applicable to the split construct so there is no way to coordinate between multiple threads within a split like we can in a partitioned step. In the case of a split we may want to have multiple steps run in parallel and then have some way to "analyze" the data as well.
You are correct there is no way for application code to interpose on the batch status and exit status of the flows within a split. However, the split can pass control to a decider. The decider has visibility to the SplitContext. If we store the results of each of the flows within the SplitContext, then the Decider could make an informed decision.
The spec was updated so the split context has a list of results from each flow in the split. This way the decider can see all that happened in the split and make a decision accordingly.