[ https://issues.apache.org/jira/browse/UIMA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656131#action_12656131 ]
Burn Lewis commented on UIMA-1245: ---------------------------------- Marshall's generalization to apply process-parent-last to any delegate, not just the first after a CM, would probably be only useful with a custom Flow Controller, so perhaps it should be controlled via the FC. If we added a "wait-for-children" flag to each Step object then when set true the framework could suspend the flow of any CAS with active children. When all children are released the controller would process the parent's flow. We're currently doing this just for the FinalStep but generalizing to any Step would be easy. (The flag would always be set for FinalStep as all children must complete without errors before the parent is released.) We could add a new "wait" choice to the ActionAfterCasMultiplier configuration parameter in the Fixed & Advanced FCs > Processing order of parent CAS different on UIMA and UIMA AS > ------------------------------------------------------------ > > Key: UIMA-1245 > URL: https://issues.apache.org/jira/browse/UIMA-1245 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Reporter: Eddie Epstein > > Arron Kaplan raised the question of when parent CASes are processed relative > to their children. See http://markmail.org/message/5cop7iv2nshouhgs As of > now, the processing order for a multi-threaded UIMA AS aggregate is different > than that for a single-threaded UIMA aggregate. > A discussion with Burn, Adam, Jerry, Marshall and myself concluded that the > default processing order for UIMA AS should be changed to be the same as in > UIMA, in order to have the same application behavior for both. This will be > done by suspending flow of a parent CAS after it is returned from a > CasMultiplier delegate until all its children CASes have finished processing. > However, there also needs to be a UIMA AS deployment option for CasMultiplier > delegates that allows the parent CAS to resume processing immediately after > being returned from the CM. This option is needed to enable parallel > processing. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.