[
https://issues.apache.org/jira/browse/UIMA-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654598#action_12654598
]
Adam Lally commented on UIMA-1245:
----------------------------------
Actually I think your proposal to block the parent upon return to the AGGR
~outer~ is already implied by the original proposal. That's because AGGR
~inner~ is a CAS Multiplier, and therefore its parent CAS should be blocked
from further processing until its children have finished processing in AGGR
~outer~.
It's a good point though that this wouldn't be exactly identical to the
single-threaded case. The relative order of 2 components being executed would
be the same as the synchronous case whenever those 2 components were "sibilngs"
(contained in the same aggregate, at the same level of nesting), but not when
they were at different levels of nesting. I think that's still good enough,
though.
> 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.
