[ https://issues.apache.org/jira/browse/UIMA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676750#action_12676750 ]
Burn Lewis commented on UIMA-1245: ---------------------------------- My suggestion that we should attempt to emulate core UIMA's single-threaded handling of parents was clearly over-design .... when all that appears to be needed is a way to optionally ensure that parents follow children in the flow. I assume that in 3) you mean that the parameter is part of the CasMultiplier specification in the deployment descriptor for the aggregate, i.e. applies per CasMultiplier and not to all CasMulti[pliers in the aggregate. Since the default (I hope) will be to let the parent continue in the flow as soon as its last child has entered the flow, perhaps the parameter for this new feature could indicate that the parent's processing will be suspended until all its child CASes have completed their processing in the aggregate. Since the docs use the terms input/output instead of parent/child perhaps... <casMultiplier poolSize="6" suspendInputCas="true"/> or <casMultiplier poolSize="6" processInputCasAfterOutputs="true"/> +1 for the simpler per-aggregate design > 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.