Bug 4183 - There is no way to access the parent job context at the end of a Split
There is no way to access the parent job context at the end of a Split
Product: jbatch
Classification: Unclassified
Component: source
PC Windows
: P5 normal
: ---
Assigned To: cvignola
Depends on:
  Show dependency treegraph
Reported: 2012-10-03 19:39 UTC by kmukher
Modified: 2013-01-16 23:02 UTC (History)
1 user (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description kmukher 2012-10-03 19:39:02 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.
Comment 1 cvignola 2012-10-05 18:51:54 UTC
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.
Comment 2 cvignola 2013-01-16 16:08:25 UTC
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.